From: jamal <hadi@cyberus.ca>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
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 09:03:58 -0400 [thread overview]
Message-ID: <1190034238.4230.113.camel@localhost> (raw)
In-Reply-To: <20070917102738.GA3087@2ka.mipt.ru>
On Mon, 2007-17-09 at 14:27 +0400, Evgeniy Polyakov wrote:
>
> How many cpu collisions you are seeing?
On 4 CPUs which were always transmitting very few - there was contention
in the range of 100 per million attempts.
Note: it doesnt matter that 4 cpus were busy, this lock is contended at
max (for all NAPI drivers i poked into) between two CPUs.
> Did I understand you right, that you replaced trylock with lock and
> thus removed collision handling and got better results?
Yes, a small one with the 4 CPUs and no irq binding. Note that in the
test cases i run, the contention for queue lock was high (since all CPUs
were busy processing traffic).
I think as the the number of CPUs go up, this will become more
prominent. The choice is between contending for queue lock or this lock.
One lock is contended by max of two cpus, the other by N cpus. As N goes
up, you want to have more mercy on the one that is contended by N cpus.
Did that make sense?
cheers,
jamal
next prev parent reply other threads:[~2007-09-17 13:04 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 [this message]
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=1190034238.4230.113.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 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).