From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next-2.6] ipv4: add rcu annotations in route.c
Date: Fri, 17 Sep 2010 21:59:33 +0200 [thread overview]
Message-ID: <1284753573.4373.7.camel@edumazet-laptop> (raw)
In-Reply-To: <1284739159.3391.95.camel@edumazet-laptop>
Le vendredi 17 septembre 2010 à 17:59 +0200, Eric Dumazet a écrit :
> Use __rcu attribute where appropriate.
>
> Use rcu_dereference_raw() in contexts where no lock is held.
>
> Use rcu_dereference_check() in contexts where the chain spinlock is
> held.
Hmm, it should be rcu_dereference_protected(), I'll send a v2
This is a bit tricky ...
next prev parent reply other threads:[~2010-09-17 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 15:59 [PATCH net-next-2.6] ipv4: add rcu annotations in route.c Eric Dumazet
2010-09-17 19:59 ` Eric Dumazet [this message]
2010-09-17 22:59 ` 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=1284753573.4373.7.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--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