From: Stephen Hemminger <shemminger@vyatta.com>
To: Wang Chen <wangchen@cn.fujitsu.com>
Cc: "David S. Miller" <davem@davemloft.net>, NETDEV <netdev@vger.kernel.org>
Subject: Re: [PATCH] FIB_TRIE: RCU refine
Date: Thu, 20 Mar 2008 08:35:44 -0700 [thread overview]
Message-ID: <20080320083544.581d309c@extreme> (raw)
In-Reply-To: <47E1F2DB.20204@cn.fujitsu.com>
> David, sorry to send this patch again.
> I sent it yesterday, but seems that it was refused by
> netdev maillist. I subscribed the mailist and send it
> again.
>
> On reader side, RCU list-traversal functions, such as
> *list_for_each_entry_rcu(), should be within an RCU
> read-side critical section.
>
> Surround them by rcu_read_*lock()
This patch is unnecessary since rcu_read_lock is already fib_trie_seq_start
and fib_trie_seq_stop.
next prev parent reply other threads:[~2008-03-20 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 5:15 [PATCH] FIB_TRIE: RCU refine Wang Chen
2008-03-20 5:19 ` David Miller
2008-03-20 15:35 ` Stephen Hemminger [this message]
2008-03-20 22:14 ` David Miller
2008-03-21 0:19 ` Wang Chen
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=20080320083544.581d309c@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=wangchen@cn.fujitsu.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).