From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Thomas Graf <tgraf@suug.ch>
Subject: Re: [PATCH 1/1][PKT_CLS] Avoid multiple tree locks
Date: Fri, 23 Mar 2007 09:12:58 -0400 [thread overview]
Message-ID: <1174655578.4930.12.camel@localhost> (raw)
In-Reply-To: <46026A31.1090603@trash.net>
On Thu, 2007-22-03 at 12:36 +0100, Patrick McHardy wrote:
> jamal wrote:
> > On Wed, 2007-21-03 at 15:04 +0100, Patrick McHardy wrote:
> 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.
>
ok, that would work. Should have been obvious to me.
cheers,
jamal
next prev parent reply other threads:[~2007-03-23 13:13 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 [this message]
2007-03-27 23:44 ` David Miller
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=1174655578.4930.12.camel@localhost \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--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).