Commit d9b96847 authored by Mike Hibler's avatar Mike Hibler

Kernel mbuf sizing no longer needed as of FreeBSD 10.x.

parent 46c27d18
...@@ -4,10 +4,6 @@ beastie_disable="YES" ...@@ -4,10 +4,6 @@ beastie_disable="YES"
# Shorten this to allow faster boots # Shorten this to allow faster boots
autoboot_delay="5" autoboot_delay="5"
## for wireless nodes
#if_ath_load="YES"
#hw.bge.allow_asf=1
# #
# If you are using an extra, regular (i.e., visible to the OS) Ethernet port # If you are using an extra, regular (i.e., visible to the OS) Ethernet port
# for your management interface, then you should disable it so that FreeBSD # for your management interface, then you should disable it so that FreeBSD
...@@ -26,35 +22,13 @@ hw.memtest.tests=0 ...@@ -26,35 +22,13 @@ hw.memtest.tests=0
hw.mfi.mrsas_enable=1 hw.mfi.mrsas_enable=1
# #
# Some drivers, most notably the Intel 10Gb "ixgbe" driver and newer 1Gb # N.B. As of FreeBSD 10.1, you don't need to tweak these, the defaults
# drivers, are very liberal with their mbuf allocation for RX buffers. # are plenty big!
# The ixgbe driver in particular wants to allocate up to 2048 buffers
# per interface per CPU core (up to 8). On the Utah d820 nodes that is
# 2048 * 4 * 8 == 65536 mbufs.
#
# This can cause dhclient to fail when it fires up all interfaces at once
# and the kernel runs out of mbufs.
#
# At Utah we avoid this by not dhcp'ing on the "ix" interfaces (see
# /etc/rc.d/netif-emulab) because they are never the control net. But if
# you have a 10Gb control net, or some other interface that allocates
# excessive mbufs, you may need to try the following settings or something
# even larger. Note that the relationship between the four values is the
# same as what FreeBSD uses for the defaults; i.e., each value is half the
# preceding value.
#
# Someday, these values will get re-adjusted in the Emulab startup scripts
# to a more appropriate value based on the size of RAM and total number of
# interfaces.
#
# As of January 2016, we now have new nodes that have a total of 6
# problematic interfaces each along with 16 cores, so we had to bump this
# even higher!
# #
kern.ipc.nmbclusters=262144 #kern.ipc.nmbclusters=262144
kern.ipc.nmbjumbop=131072 #kern.ipc.nmbjumbop=131072
kern.ipc.nmbjumbo16=65536 #kern.ipc.nmbjumbo16=65536
kern.ipc.nmbjumbo9=32768 #kern.ipc.nmbjumbo9=32768
# force module path, our pxeboot can mess it up # force module path, our pxeboot can mess it up
module_path="/boot/kernel;/boot/modules" module_path="/boot/kernel;/boot/modules"
......
...@@ -22,35 +22,13 @@ hw.memtest.tests=0 ...@@ -22,35 +22,13 @@ hw.memtest.tests=0
hw.mfi.mrsas_enable=1 hw.mfi.mrsas_enable=1
# #
# Some drivers, most notably the Intel 10Gb "ixgbe" driver and newer 1Gb # N.B. As of FreeBSD 10.1, you don't need to tweak these, the defaults
# drivers, are very liberal with their mbuf allocation for RX buffers. # are plenty big!
# The ixgbe driver in particular wants to allocate up to 2048 buffers
# per interface per CPU core (up to 8). On the Utah d820 nodes that is
# 2048 * 4 * 8 == 65536 mbufs.
# #
# This can cause dhclient to fail when it fires up all interfaces at once #kern.ipc.nmbclusters=262144
# and the kernel runs out of mbufs. #kern.ipc.nmbjumbop=131072
# #kern.ipc.nmbjumbo16=65536
# At Utah we avoid this by not dhcp'ing on the "ix" interfaces (see #kern.ipc.nmbjumbo9=32768
# /etc/rc.d/netif-emulab) because they are never the control net. But if
# you have a 10Gb control net, or some other interface that allocates
# excessive mbufs, you may need to try the following settings or something
# even larger. Note that the relationship between the four values is the
# same as what FreeBSD uses for the defaults; i.e., each value is half the
# preceding value.
#
# Someday, these values will get re-adjusted in the Emulab startup scripts
# to a more appropriate value based on the size of RAM and total number of
# interfaces.
#
# As of January 2016, we now have new nodes that have a total of 6
# problematic interfaces each along with 16 cores, so we had to bump this
# even higher!
#
kern.ipc.nmbclusters=262144
kern.ipc.nmbjumbop=131072
kern.ipc.nmbjumbo16=65536
kern.ipc.nmbjumbo9=32768
# force module path, our pxeboot can mess it up # force module path, our pxeboot can mess it up
module_path="/boot/kernel;/boot/modules" module_path="/boot/kernel;/boot/modules"
......
...@@ -22,35 +22,13 @@ hw.memtest.tests=0 ...@@ -22,35 +22,13 @@ hw.memtest.tests=0
hw.mfi.mrsas_enable=1 hw.mfi.mrsas_enable=1
# #
# Some drivers, most notably the Intel 10Gb "ixgbe" driver and newer 1Gb # N.B. As of FreeBSD 10.1, you don't need to tweak these, the defaults
# drivers, are very liberal with their mbuf allocation for RX buffers. # are plenty big!
# The ixgbe driver in particular wants to allocate up to 2048 buffers
# per interface per CPU core (up to 8). On the Utah d820 nodes that is
# 2048 * 4 * 8 == 65536 mbufs.
# #
# This can cause dhclient to fail when it fires up all interfaces at once #kern.ipc.nmbclusters=262144
# and the kernel runs out of mbufs. #kern.ipc.nmbjumbop=131072
# #kern.ipc.nmbjumbo16=65536
# At Utah we avoid this by not dhcp'ing on the "ix" interfaces (see #kern.ipc.nmbjumbo9=32768
# /etc/rc.d/netif-emulab) because they are never the control net. But if
# you have a 10Gb control net, or some other interface that allocates
# excessive mbufs, you may need to try the following settings or something
# even larger. Note that the relationship between the four values is the
# same as what FreeBSD uses for the defaults; i.e., each value is half the
# preceding value.
#
# Someday, these values will get re-adjusted in the Emulab startup scripts
# to a more appropriate value based on the size of RAM and total number of
# interfaces.
#
# As of January 2016, we now have new nodes that have a total of 6
# problematic interfaces each along with 16 cores, so we had to bump this
# even higher!
#
kern.ipc.nmbclusters=262144
kern.ipc.nmbjumbop=131072
kern.ipc.nmbjumbo16=65536
kern.ipc.nmbjumbo9=32768
# force module path, our pxeboot can mess it up # force module path, our pxeboot can mess it up
module_path="/boot/kernel;/boot/modules" module_path="/boot/kernel;/boot/modules"
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment