From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, saeedm@mellanox.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: use rhashtable_lookup() instead of rhashtable_lookup_fast()
Date: Sat, 23 Nov 2019 12:17:08 -0800 [thread overview]
Message-ID: <20191123121708.3b459aef@cakuba.netronome.com> (raw)
In-Reply-To: <20191122081519.20918-1-ap420073@gmail.com>
On Fri, 22 Nov 2019 08:15:19 +0000, Taehee Yoo wrote:
> rhashtable_lookup_fast() internally calls rcu_read_lock() then,
> calls rhashtable_lookup(). So if rcu_read_lock() is already held,
> rhashtable_lookup() is enough.
>
> Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Applied, thanks!
prev parent reply other threads:[~2019-11-23 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 8:15 [PATCH net-next] net: use rhashtable_lookup() instead of rhashtable_lookup_fast() Taehee Yoo
2019-11-23 20:17 ` Jakub Kicinski [this message]
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=20191123121708.3b459aef@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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).