From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: Patrick McHardy <kaber@trash.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 RCU breakage in dev_queue_xmit
Date: Tue, 09 Nov 2004 11:40:26 -0700 [thread overview]
Message-ID: <41910F1A.8070305@drdos.com> (raw)
In-Reply-To: <419108ED.9090608@trash.net>
Patrick McHardy wrote:
> Jeff V. Merkey 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:
>>
>> Nov 8 15:38:08 ds kernel: Badness in local_bh_enable at
>> kernel/softirq.c:141
>> Nov 8 15:38:08 ds kernel: [<40107d1e>] dump_stack+0x1e/0x30
>> Nov 8 15:38:08 ds kernel: [<401218b0>] local_bh_enable+0x70/0x80
>> Nov 8 15:38:08 ds kernel: [<402c5bbb>] dev_queue_xmit+0x11b/0x250
>> Nov 8 15:38:08 ds kernel: [<f8981cb7>] xmit_skb+0x17/0x20 [dsfs]
>> Nov 8 15:38:08 ds kernel: [<f8981f8e>] xmit_packet+0x2e/0x80 [dsfs]
>> Nov 8 15:38:08 ds kernel: [<f89820eb>] regen_data+0x10b/0x290 [dsfs]
>
>
> There is no such function in the 2.6.9 kernel.
Check /include/linux for local_bh_enable and /net/core/dev.c .
Jeff
>
> Regards
> Patrick
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-11-09 18:18 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 [this message]
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
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=41910F1A.8070305@drdos.com \
--to=jmerkey@drdos.com \
--cc=kaber@trash.net \
--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.