Re: 10G and socket alloc failure
- From: Andre Oppermann <andre@xxxxxxxxxxx>
- Date: Thu, 19 Jul 2007 10:13:38 +0200
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
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: 10G and socket alloc failure
- From: Jack Vogel
- Re: 10G and socket alloc failure
- References:
- 10G and socket alloc failure
- From: Jack Vogel
- 10G and socket alloc failure
- Prev by Date: Re: uhidev(4) update - USB HID driver level for devices with multiple report ids
- Next by Date: Re: 10G and socket alloc failure
- Previous by thread: 10G and socket alloc failure
- Next by thread: Re: 10G and socket alloc failure
- Index(es):
Relevant Pages
|
|
