Oops, we surely have kern.ipc.nmbclusters="0" in loader.conf, but I
think that should not modify net.inet.tcp.reass.maxsegments to "0"
since we wish unlimited nmbclusters but not zero TCP reassembly
segments.
On Tue, Jan 6, 2009 at 4:16 PM, Robert Watson wrote:
>
> On Tue, 6 Jan 2009, Lin Jui-Nan
On Tue, 6 Jan 2009, Lin Jui-Nan Eric wrote:
I thought that the system auto-tune improperly in this case.
Hmm. Do you have a custom setting for kern.ipc.nmbclusters in loader.conf or
sysctl.conf? What does kern.ipc.nmbclusters configure itself to on your
system? Also, could you send me th
Hi Robert,
I thought that the system auto-tune improperly in this case.
On Mon, Jan 5, 2009 at 9:13 PM, Robert Watson wrote:
> On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote:
>
>> After running "netstat -s -p tcp", we found that lots of packets are
>> discarded due to memory problems. We googled for
On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote:
After running "netstat -s -p tcp", we found that lots of packets are
discarded due to memory problems. We googled for it, and found that sysctl
oid "net.inet.tcp.reass.maxsegments" became 0, therefore packets never
reassembled.
Then we checked our
Dear All listers,
After running "netstat -s -p tcp", we found that lots of packets are
discarded due to memory problems. We googled for it, and found that
sysctl oid "net.inet.tcp.reass.maxsegments" became 0, therefore
packets never reassembled.
Then we checked our /boot/loader.conf and /etc/sysc
