From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 RCU breakage in dev_queue_xmit
Date: Wed, 10 Nov 2004 16:56:25 -0700 [thread overview]
Message-ID: <4192AAA9.7080407@drdos.com> (raw)
In-Reply-To: <E1CRhaw-0001v7-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
>Jeff V. Merkey <jmerkey@drdos.com> wrote:
>
>
>>Running dual gigabit interfaces at 196 MB/S (megabytes/second) on
>>receive, 12 CLK interacket gap time, 1500 bytes payload
>>at 65000 packets per second per gigabit interface, and retransmitting
>>received packets at 130 MB/S out of a third gigabit interface
>>with skb, RCU locks in dev_queue_xmit breaks and enters the following state:
>>
>>
>
>This patch might help.
>
>
Herbert,
Even with this patch I still see RCU breakage at these data rates and
the problem persists -- it just takes
longer for it to manifest (about 23 hours). I am recoding
dev_queue_xmit since the use of RCU primitives
is severely busted. I looked over the code and the fact it breaks on
uniprocessor is really a joke.
No offense guys, but this is pretty bad. How about something simple,
like a spinlock or
multiple send queues per proc?
Jeff
prev parent reply other threads:[~2004-11-10 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 17:35 2.6.9 RCU breakage in dev_queue_xmit Jeff V. Merkey
2004-11-09 18:14 ` Patrick McHardy
2004-11-09 18:40 ` Jeff V. Merkey
2004-11-09 18:37 ` Stephen Hemminger
2004-11-09 23:38 ` Jeff V. Merkey
2004-11-10 1:48 ` Herbert Xu
2004-11-10 17:21 ` Jeff V. Merkey
2004-11-10 23:56 ` Jeff V. Merkey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4192AAA9.7080407@drdos.com \
--to=jmerkey@drdos.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.