From: Stephen Hemminger <shemminger@vyatta.com>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: netdev@vger.kernel.org,
Lucian Adrian Grijincu <lucian.grijincu@gmail.com>,
Vlad Dogaru <ddvlad@rosedu.org>
Subject: Re: [PATCH net-next-2.6 v2] net: factorize sync-rcu call in unregister_netdevice_many
Date: Mon, 13 Dec 2010 15:32:59 -0800 [thread overview]
Message-ID: <20101213153259.1bfedb15@nehalam> (raw)
In-Reply-To: <1292277293-6565-1-git-send-email-opurdila@ixiacom.com>
On Mon, 13 Dec 2010 23:54:53 +0200
Octavian Purdila <opurdila@ixiacom.com> wrote:
> + /*
> + * Tell people we are going down, so that they can
> + * prepare to death, when device is still operating.
> + */
> + call_netdevice_notifiers(NETDEV_GOING_DOWN, dev);
Never liked the repeated notifier. It was a dumb idea, there is
no reason to believe that repeatedly whacking a notifier is going
to make device get released.
--
prev parent reply other threads:[~2010-12-13 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 21:54 [PATCH net-next-2.6 v2] net: factorize sync-rcu call in unregister_netdevice_many Octavian Purdila
2010-12-13 23:32 ` Stephen Hemminger [this message]
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=20101213153259.1bfedb15@nehalam \
--to=shemminger@vyatta.com \
--cc=ddvlad@rosedu.org \
--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;
as well as URLs for NNTP newsgroup(s).