From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: pktgen and spin_lock_bh in xmit path
Date: Mon, 19 Oct 2009 20:38:03 -0700 [thread overview]
Message-ID: <4ADD309B.1040505@candelatech.com> (raw)
I'm having strange issues when running pktgen on 10G interfaces while
also running
pktgen on mac-vlans on that interface, when the mac-vlan pktgen threads
are on a different
CPU.
First, lockdep gives up and says that things are not properly
annotated. I believe this is because
the macvlan tx path will lock it's txq and will also lock the
lower-dev's txq. To fix this, perhaps
we need some new lockdep aware primitives for netdev txq locking?
Second, is using _bh() locking really sufficient if we have pktgen
writing to a physical device
and also have other pktgen threads writing to that same device though
mac-vlans? I'm seeing
deadlocks spinning on the _bh() lock in pktgen as well as strange
corruptions, so I think there
must be *some* problem somewhere, I just don't know quite what it is yet.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2009-10-20 3:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 3:38 Ben Greear [this message]
2009-10-20 3:48 ` pktgen and spin_lock_bh in xmit path Eric Dumazet
2009-10-20 4:52 ` Ben Greear
2009-10-20 17:37 ` Ben Greear
2009-10-20 17:44 ` Eric Dumazet
2009-10-20 17:54 ` Ben Greear
2009-10-20 18:35 ` Eric Dumazet
2009-10-20 18:54 ` Eric Dumazet
2009-10-20 20:16 ` Ben Greear
2009-10-20 21:10 ` Ben Greear
2009-10-20 21:22 ` Eric Dumazet
2009-10-20 21:30 ` Ben Greear
2009-10-20 21:57 ` Eric Dumazet
2009-10-20 23:17 ` Ben Greear
2009-10-21 3:05 ` Ben Greear
2009-10-21 3:12 ` Eric Dumazet
2009-10-21 3:59 ` Eric Dumazet
2009-10-21 5:00 ` Ben Greear
2009-10-21 5:14 ` Eric Dumazet
2009-10-21 5:40 ` Ben Greear
2009-10-21 5:12 ` Krishna Kumar2
2009-10-21 5:32 ` Ben Greear
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=4ADD309B.1040505@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).