Date: Thu, 19 Jul 2007 10:13:38 +0200 From: Andre Oppermann <andre@freebsd.org> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: 10G and socket alloc failure Message-ID: <469F1D32.2040700@freebsd.org> In-Reply-To: <2a41acea0707181542q23d36733o339448ad86f480cb@mail.gmail.com> References: <2a41acea0707181152r4c662b00tf1be7b6b4dce74f1@mail.gmail.com> <2a41acea0707181542q23d36733o339448ad86f480cb@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote: > While testing out the ixgbe driver we've observed this failure in the stack > code, here is the info: > > The test engineer is using iperf, typically with 16 threads. If the > driver is using > either legacy or MSI interrupts we will see broken pipes, in dmesg its > due to sonewconn() failing in syncache_socket(). > > Whats interesting is that when I have multiple RX queues configured and > using MSI/X this doesnt happen, at least not very often. > > It does not seem to hurt performance horribly, iperf just spawns another > thread, but I was wondering if there is some underlying tuneable I dont > know about that would stop this from happening?? > > And any theory about why it doesnt happen with multiple queues? Do you see any messages in syslog regarding syncache? -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?469F1D32.2040700>