Searched hist:77900 (Results 1 - 10 of 10) sorted by relevance
| /freebsd-11-stable/sys/kern/ | ||
| H A D | kern_environment.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| H A D | kern_ktr.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| H A D | kern_malloc.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| H A D | uipc_sockbuf.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| H A D | uipc_mbuf.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| H A D | subr_witness.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| /freebsd-11-stable/sys/net/ | ||
| H A D | if_loop.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| /freebsd-11-stable/sys/dev/sound/pcm/ | ||
| H A D | sound.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| /freebsd-11-stable/sys/sys/ | ||
| H A D | kernel.h | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
| /freebsd-11-stable/sys/netinet/ | ||
| H A D | tcp_timewait.c | diff 77900 Fri Jun 08 03:24:21 MDT 2001 peter "Fix" the previous initial attempt at fixing TUNABLE_INT(). This time around, use a common function for looking up and extracting the tunables from the kernel environment. This saves duplicating the same function over and over again. This way typically has an overhead of 8 bytes + the path string, versus about 26 bytes + the path string. |
Completed in 580 milliseconds