From: David Miller <davem@davemloft.net>
To: kaber@trash.net
Cc: hadi@cyberus.ca, netdev@vger.kernel.org, tgraf@suug.ch
Subject: Re: [PATCH 1/1][PKT_CLS] Avoid multiple tree locks
Date: Tue, 27 Mar 2007 16:44:35 -0700 (PDT) [thread overview]
Message-ID: <20070327.164435.123974053.davem@davemloft.net> (raw)
In-Reply-To: <46026A31.1090603@trash.net>
From: Patrick McHardy <kaber@trash.net>
Date: Thu, 22 Mar 2007 12:36:17 +0100
> jamal wrote:
> > The mutex is certainly a cleaner approach;
> > and a lot of the RCU protection would go away. I like it.
>
> Not as much as I initially thought, but at least we would have
> consistent locking for the dump callbacks.
>
> > Knowing you i sense theres something clever in there that i am
> > missing. I dont see how you could get rid of the tree locking
> > since we need to protect against the data path still, no?
> > Or are you looking at that as a separate effort?
>
> We can remove qdisc_tree_lock since with this patch all changes
> and all tree walking happen under the RTNL. We still need to keep
> dev->queue_lock for the data path.
>
> I'll update the patches to include all rtnetlink users and repost
> in a day or two.
The existing weird "first SKB only" locking is unintuitive to
me as well, so I'm all for these mutex patches once you respin
them FWIW.
next prev parent reply other threads:[~2007-03-27 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 9:58 [PATCH 1/1][PKT_CLS] Avoid multiple tree locks jamal
2007-03-21 10:10 ` Patrick McHardy
2007-03-21 10:17 ` Patrick McHardy
2007-03-21 12:35 ` Patrick McHardy
2007-03-21 14:04 ` Patrick McHardy
2007-03-21 14:06 ` Patrick McHardy
2007-03-22 6:07 ` jamal
2007-03-22 11:36 ` Patrick McHardy
2007-03-23 13:12 ` jamal
2007-03-27 23:44 ` David Miller [this message]
2007-03-21 10:38 ` jamal
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=20070327.164435.123974053.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).