From: Jarek Poplawski <jarkao2@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH]: Kill qdisc rcu freeing...
Date: Mon, 18 Aug 2008 12:07:25 +0000 [thread overview]
Message-ID: <20080818120725.GB7393@ff.dom.local> (raw)
In-Reply-To: <20080817.223435.193704624.davem@davemloft.net>
On Sun, Aug 17, 2008 at 10:34:35PM -0700, David Miller wrote:
>
> Ok, I flipped the switch. I've checked in the following to
> net-2.6 and it seems to pass a bunch of smoke tests I just
> did (flood pings while adding and deleting various qdisc
> setups, etc.)
>
> Jarek, I think we can possibly now revert that locking change
> you had to make because destroy was outside of RTNL?
Yes, I think there are these two patches only to revert:
----------
commit d4766692e72422f3b0f0e9ac6773d92baad07d51
Author: Jarek Poplawski <jarkao2@gmail.com>
Date: Wed Aug 13 15:20:24 2008 -0700
pkt_sched: Protect gen estimators under est_lock.
----------
commit 1cfa26661a85549063e369e2b40275eeaa7b923c
Author: Jarek Poplawski <jarkao2@gmail.com>
Date: Mon Aug 11 18:11:06 2008 -0700
pkt_sched: Add BH protection for qdisc_stab_lock.
----------
I guess, I don't need to send any patches, but let me know if I'm
wrong.
Thanks,
Jarek P.
>
> pkt_sched: No longer destroy qdiscs from RCU.
>
> We can now kill them synchronously with all of the
> previous dev_deactivate() cures.
>
> This makes netdev destruction and shutdown saner as
> the qdiscs hold references to the device.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
...
next prev parent reply other threads:[~2008-08-18 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 5:34 [PATCH]: Kill qdisc rcu freeing David Miller
2008-08-18 12:07 ` Jarek Poplawski [this message]
2008-08-19 5:33 ` 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=20080818120725.GB7393@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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