Re: bge dropping packets issue
- From: Jung-uk Kim <jkim@xxxxxxxxxxx>
- Date: Wed, 16 Apr 2008 14:56:18 -0400
[CC trimmed]
On Wednesday 16 April 2008 02:20 pm, Alexander Sack wrote:
Dieter: Thanks, at 20Mbps! That's pretty aweful.
JK: Thanks again. Wow, I searched the list and didn't see much
discussion with respect to bge and packet loss! I will try the
rest of that patch including pushing the TCP receive buffer up
(though I don't think that's going to help in this case). The
above is based on just looking at code....
I guess some follow-up questions would be:
1) Why isn't BGE_SSLOTS tunable (to a point)? Why can't that be
added the driver? I noticed that CURRENT has added a lot more
SYSCTL information. Moreover it seems the Linux driver can set it
up to 1024.
IIRC, Linux tg3 uses one ring for both standard and jumbo.
2) bge_tick() uses the same global mutex for its callout as the
rest of the driver. Moreover, it really doesn't have to hold it
while updating statistics, they are reads of volatile registers
anyway (blocking the ISR doesn't prevent the firmware from updating
its stat struct). Would there be any interest in using a separate
mutex for the callout itself and then just hold the lock for the
other small calls (bge_asf_driver_up(), bge_watchdog())? I'm
experimenting with right now just dropping the BGE mutex around the
bge_stats_update() calls to give more time to bge_rxeof() to drain
rx_bd's. I admit that bge_tick doesn't do a whole lot but it seems
this driver is very sensitive to resource starvation and I'm trying
to get the BGE driver to drain as much rx_bd's as possible to avoid
drops due to the firmware having no place to put them!
3) How does interrupt non-DEVICE_POLLING perform?
If you just use default values, it won't perform very well. There are
some patches around the net to automatically adjust these numbers,
e.g.,
http://docs.freebsd.org/cgi/mid.cgi?20071117194615.L67319
http://mail-index.netbsd.org/tech-kern/2004/03/16/0000.html
Jung-uk Kim
Thanks guys!<freebsd@xxxxxxxxxxxxxxxxxxxx> wrote:
-aps
On Wed, Apr 16, 2008 at 5:32 AM, Dieter
_______________________________________________I'm investigating an issue we are seeing with 6.1-RELEASE and> driver dropping packets sporadically at 100MBps speed.
the bge
> wrong tree with my initial investigation? Does anyone know if
Its get mainly aggravated when heavy disk I/O occurs
Has anyone seen this problem before with bge? Am I barking up
the
> its even possible to achieve 100% packet capture with bge at
> its supported speeds (10/100/1000)?
I had a similar problem with bge and 6.0-RELEASE. Bge works
great for me in 6.2-RELEASE. So far 7.0-RELEASE looks good as
well (bge-wise, I do have unresolved issues with 7).
My app is TCP, cranking the TCP receive buffer way up helped, as
did turning off Nagle.
My bge is 1000, but connected at 100 since that is what the
other end is. I saw problems at less than 20 Mbps.
There is still a problem that other drivers can lock out bge for
too long. For example kern/118093: firewire bus reset.
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: bge dropping packets issue
- From: Alexander Sack
- Re: bge dropping packets issue
- References:
- bge dropping packets issue
- From: Alexander Sack
- Re: bge dropping packets issue
- From: Dieter
- Re: bge dropping packets issue
- From: Alexander Sack
- bge dropping packets issue
- Prev by Date: Re: bge dropping packets issue
- Next by Date: [patch] ng_iface(4) and ports/net/mpd4 allow renaming of interfaces.
- Previous by thread: Re: bge dropping packets issue
- Next by thread: Re: bge dropping packets issue
- Index(es):
Relevant Pages
|
|
