From: Stephen Hemminger <shemminger@vyatta.com>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org,
"Lucian Adrian Grijincu" <lucian.grijincu@gmail.com>,
Vlad Dogaru <ddvlad@rosedu.org>
Subject: Re: [PATCH net-next-2.6] net: add dev_close_many
Date: Mon, 13 Dec 2010 15:34:09 -0800 [thread overview]
Message-ID: <20101213153409.47603d24@nehalam> (raw)
In-Reply-To: <201012132254.24267.opurdila@ixiacom.com>
On Mon, 13 Dec 2010 22:54:24 +0200
Octavian Purdila <opurdila@ixiacom.com> wrote:
> From: Stephen Hemminger <shemminger@vyatta.com>
> Date: Monday 13 December 2010, 20:04:47
>
> > I assume the need for dev_close_many is coming from a user space
> > application?
> >
> > I expect that for this kind of special need, you would be better off not
> > using the normal iproute utilities and instead have a custom device manager
> > that is doing netlink directly.
> >
> > Rather than doing synchronous send request and wait for ack. The utility
> > could use a sender and collector thread.
>
> Actually we need dev_close_many in order to speed up netdev_unregister_many
> since in the netdev_unregister_many path there is still one more sync-rcu
> operation which is not factorized.
>
> I will prepare v2 to address David's comment and I will also be more explicit
> in the commit message.
That makes sense.
--
next prev parent reply other threads:[~2010-12-13 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 14:18 [PATCH net-next-2.6] net: add dev_close_many Octavian Purdila
2010-12-13 16:52 ` Eric Dumazet
2010-12-13 17:23 ` Octavian Purdila
2010-12-13 17:32 ` Stephen Hemminger
2010-12-13 17:52 ` Octavian Purdila
2010-12-13 18:04 ` Stephen Hemminger
2010-12-13 20:54 ` Octavian Purdila
2010-12-13 23:34 ` Stephen Hemminger [this message]
2010-12-13 17:54 ` 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=20101213153409.47603d24@nehalam \
--to=shemminger@vyatta.com \
--cc=ddvlad@rosedu.org \
--cc=eric.dumazet@gmail.com \
--cc=lucian.grijincu@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.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