From: jamal <hadi@cyberus.ca>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org,
kaber@trash.net, dada1@cosmosbay.com, johnpol@2ka.mipt.ru
Subject: Re: [RFC][NET_SCHED] explict hold dev tx lock
Date: Wed, 19 Sep 2007 09:33:52 -0400 [thread overview]
Message-ID: <1190208832.4259.6.camel@localhost> (raw)
In-Reply-To: <1190083728.4237.59.camel@localhost>
On Mon, 2007-17-09 at 22:48 -0400, jamal wrote:
> Nothing much has changed from what it was before.
> The only difference is we let go of the queue lock before grabbing
> the tx lock which never mattered for LLTX.
> Once we grab the tx lock it is the same logic and so far is working well
> on both tg3 and e1000 (which is LLTX).
> I will continue to retest with net-2.6.24 once you complete rebasing
> and look around to see if anyone maybe affected.
Ok, this is looking solid with this mornings tree. Tested on a dual core
xeon with e1000 (LLTX) and a dual core opteron with tg3 (non-LLTX).
About 100 million packets from udp full throttle on all 4 cpus; i tried
pulling cables etc while doing this to generate extrenous interupts and
didnt see any issues.
Shall i submit the patch?
cheers,
jamal
next prev parent reply other threads:[~2007-09-19 13:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 16:14 [RFC][NET_SCHED] explict hold dev tx lock jamal
2007-09-16 19:31 ` David Miller
2007-09-16 20:41 ` jamal
2007-09-16 20:52 ` jamal
2007-09-16 21:10 ` jamal
2007-09-17 10:27 ` Evgeniy Polyakov
2007-09-17 13:03 ` jamal
2007-09-17 13:58 ` Evgeniy Polyakov
2007-09-18 2:01 ` David Miller
2007-09-18 2:48 ` jamal
2007-09-19 13:33 ` jamal [this message]
2007-09-19 16:09 ` David Miller
2007-09-20 2:33 ` jamal
2007-09-20 2:43 ` jamal
2007-09-26 2:28 ` David Miller
2007-09-26 13:11 ` jamal
2007-10-09 4:00 ` Herbert Xu
2007-10-09 13:43 ` jamal
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=1190208832.4259.6.camel@localhost \
--to=hadi@cyberus.ca \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=johnpol@2ka.mipt.ru \
--cc=kaber@trash.net \
--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 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.