From: Eric Dumazet <eric.dumazet@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net: use synchronize_rcu_expedited()
Date: Tue, 24 May 2011 21:44:45 +0200 [thread overview]
Message-ID: <1306266285.3305.3.camel@edumazet-laptop> (raw)
In-Reply-To: <20110524192451.GH2266@linux.vnet.ibm.com>
Le mardi 24 mai 2011 à 12:24 -0700, Paul E. McKenney a écrit :
> Might make sense, though most of the gains would need to come from
> kicking the grace-period machinery hard in order to make it go faster.
>
> Interesting -- I will give this some thought.
>
I am working on a final step, using a workqueue so that the
rcu_barrier() is not done under RTNL, so it wont be anymore a blocking
point to dismantle hundred of devices per second...
Thanks
next prev parent reply other threads:[~2011-05-24 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 9:07 [PATCH] net: use synchronize_rcu_expedited() Eric Dumazet
2011-05-24 15:44 ` Paul E. McKenney
2011-05-24 15:52 ` Eric Dumazet
2011-05-24 19:24 ` Paul E. McKenney
2011-05-24 19:44 ` Eric Dumazet [this message]
2011-05-24 19:56 ` Paul E. McKenney
2011-05-24 17:28 ` David Miller
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=1306266285.3305.3.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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