From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] ipip: get rid of ipip_lock
Date: Wed, 15 Sep 2010 14:29:43 -0700 (PDT) [thread overview]
Message-ID: <20100915.142943.13758184.davem@davemloft.net> (raw)
In-Reply-To: <1284583777.2462.33.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 15 Sep 2010 22:49:37 +0200
> Le mercredi 15 septembre 2010 à 19:28 +0200, Eric Dumazet a écrit :
>> As RTNL is held while doing tunnels inserts and deletes, we can remove
>> ipip_lock spinlock. My initial RCU conversion was conservative and
>> converted the rwlock to spinlock, with no RTNL requirement.
>>
>> Use appropriate rcu annotations and modern lockdep checks as well.
>>
>> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
>
> While doing ip_gre conversion, I realize I should define a new helper
...
> I'll submit a patch serie :
>
> 1/3) net: add rtnl_dereference
> 2/3) ipip: get rid of ipip_lock
> 3/3) gre: get rid of ipgre_lock
Ok.
next prev parent reply other threads:[~2010-09-15 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 17:27 [PATCH net-next-2.6] ipip: get rid of ipip_lock Eric Dumazet
2010-09-15 20:49 ` Eric Dumazet
2010-09-15 21:29 ` David Miller [this message]
2010-09-15 21:31 ` Eric Dumazet
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=20100915.142943.13758184.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.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