Re: 10G and socket alloc failure

2007-07-19 Thread Andre Oppermann
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() fail

Re: 10G and socket alloc failure

2007-07-19 Thread Jack Vogel
On 7/19/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: 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 interru

Re: Wierd networking.

2007-07-19 Thread Eygene Ryabinkin
Julian, good day. Wed, Jul 18, 2007 at 12:12:15PM -0700, Julian Elischer wrote: > >Seems like it is the effect of the SS_NOFDREF check in the > >netinet/tcp_input.c, at least it is present in the rev. 1.281.2.5. > > > >See the post > >http://lists.freebsd.org/pipermail/freebsd-current/2007-Jul

Re: Wierd networking.

2007-07-19 Thread Julian Elischer
Eygene Ryabinkin wrote: Julian, good day. Wed, Jul 18, 2007 at 12:12:15PM -0700, Julian Elischer wrote: Seems like it is the effect of the SS_NOFDREF check in the netinet/tcp_input.c, at least it is present in the rev. 1.281.2.5. See the post http://lists.freebsd.org/pipermail/freebsd-curre

Re: Wierd networking.

2007-07-19 Thread Julian Elischer
Julian Elischer wrote: Eygene Ryabinkin wrote: Julian, good day. Wed, Jul 18, 2007 at 12:12:15PM -0700, Julian Elischer wrote: Seems like it is the effect of the SS_NOFDREF check in the netinet/tcp_input.c, at least it is present in the rev. 1.281.2.5. See the post http://lists.freebsd.or