From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Andi Kleen <ak@suse.de>
Cc: netdev@vger.kernel.org, linux-kerne@vger.kernel.org
Subject: Re: [PATCH/RFC] synchronize_rcu(): high latency on idle system
Date: Sat, 12 Jan 2008 17:52:26 -0800 [thread overview]
Message-ID: <20080112175226.7d8f9dbc@deepthought> (raw)
In-Reply-To: <200801121935.58286.ak@suse.de>
On Sat, 12 Jan 2008 19:35:58 +0100
Andi Kleen <ak@suse.de> wrote:
> On Saturday 12 January 2008 18:51:35 Benjamin LaHaise wrote:
> > On Sat, Jan 12, 2008 at 03:37:59AM +0100, Andi Kleen wrote:
> > > > And yes, the
> > > > network stack shouldn't call synchronize_rcu() quite so much, but fixing that
> > > > is a little more involved.
> > >
> > > ... but the correct solution.
> >
> > There has to be at least 1 synchronize_rcu() or equivalent in the
> > unregister_netdev() path. I suspect the easiest way to fix it might be to
> > use call_rcu() to actually free the network device, as anything else will
> > limit performance of single threaded teardown (ie, when an l2tp daemon
> > gets terminated via kill -9). This means an API change that exposes
> > rcu for unregister_netdev().
>
> The call_rcu() could be in free_netdev() couldn't it?
I think it should be in netdev_unregister_kobject(). But that would
only get rid of one of the two calls to synchronize_rcu() in the unregister_netdev.
The other synchronize_rcu() is for qdisc's and not sure if that one can
be removed?
--
Stephen Hemminger <stephen.hemminger@vyatta.com>
next parent reply other threads:[~2008-01-13 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080112012626.GI28570@kvack.org>
[not found] ` <20080112023759.GG21068@bingen.suse.de>
[not found] ` <20080112175135.GK28570@kvack.org>
[not found] ` <200801121935.58286.ak@suse.de>
2008-01-13 1:52 ` Stephen Hemminger [this message]
2008-01-13 15:34 ` [PATCH/RFC] synchronize_rcu(): high latency on idle system Andi Kleen
2008-01-14 17:19 ` Stephen Hemminger
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=20080112175226.7d8f9dbc@deepthought \
--to=shemminger@linux-foundation.org \
--cc=ak@suse.de \
--cc=linux-kerne@vger.kernel.org \
--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).