From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: jamal <hadi@cyberus.ca>
Cc: David Miller <davem@davemloft.net>,
herbert@gondor.apana.org.au, netdev@vger.kernel.org,
kaber@trash.net, dada1@cosmosbay.com
Subject: Re: [RFC][NET_SCHED] explict hold dev tx lock
Date: Mon, 17 Sep 2007 14:27:40 +0400 [thread overview]
Message-ID: <20070917102738.GA3087@2ka.mipt.ru> (raw)
In-Reply-To: <1189977000.4230.25.camel@localhost>
On Sun, Sep 16, 2007 at 05:10:00PM -0400, jamal (hadi@cyberus.ca) wrote:
> On Sun, 2007-16-09 at 16:52 -0400, jamal wrote:
>
> > What i should say is
> > if i grabbed the lock explicitly without disabling irqs it wont be much
> > different than what is done today and should always work.
> > No?
>
> And to be more explicit, heres a patch using the macros from previous
> patch. So far tested on 3 NICs.
How many cpu collisions you are seeing?
Did I understand you right, that you replaced trylock with lock and
thus removed collision handling and got better results?
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-09-17 10:29 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 [this message]
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
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=20070917102738.GA3087@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--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.