From: Eric Dumazet <eric.dumazet@gmail.com>
To: Fan Du <fan.du@windriver.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
fengguang.wu@intel.com,
Priyanka Jain <Priyanka.Jain@freescale.com>
Subject: Re: [PATCH net-next] xfrm: fix RCU bugs
Date: Mon, 20 Aug 2012 09:14:28 +0200 [thread overview]
Message-ID: <1345446868.5158.246.camel@edumazet-glaptop> (raw)
In-Reply-To: <5031DA57.1000904@windriver.com>
On Mon, 2012-08-20 at 14:33 +0800, Fan Du wrote:
> And one out of topic question:
> The usage of xfrm_state_afinfo_lock/xfrm_km_lock is extremely
> similar with xfrm_policy_afinfo_lock, except the former is not so
> frequently read than that of the later.
>
> Is it justified to convert RW xfrm_state_afinfo_lock/xfrm_km_lock into
> RCU?
>
I would say it is justified, and easy enough.
next prev parent reply other threads:[~2012-08-20 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 10:31 [PATCH net-next] xfrm: fix RCU bugs Eric Dumazet
2012-08-20 4:40 ` Fan Du
2012-08-20 5:33 ` Eric Dumazet
2012-08-20 6:33 ` Fan Du
2012-08-20 7:14 ` Eric Dumazet [this message]
2012-08-23 5:40 ` 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=1345446868.5158.246.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=Priyanka.Jain@freescale.com \
--cc=davem@davemloft.net \
--cc=fan.du@windriver.com \
--cc=fengguang.wu@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).