From: David Miller <davem@davemloft.net>
To: neilb@suse.com
Cc: tgraf@suug.ch, herbert@gondor.apana.org.au, tom@quantonium.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] rhashtable: add rhashtable_walk_last_seen()
Date: Tue, 10 Jul 2018 16:55:47 -0700 (PDT) [thread overview]
Message-ID: <20180710.165547.1599531889181336348.davem@davemloft.net> (raw)
In-Reply-To: <153086109260.2825.1459722786871837620.stgit@noble>
From: NeilBrown <neilb@suse.com>
Date: Fri, 06 Jul 2018 17:11:32 +1000
> rhashtable_walk_last_seen() returns the object returned by
> the previous rhashtable_walk_next(), providing it is still in the
> table (or was during this grace period).
> This works even if rhashtable_walk_stop() and rhashtable_talk_start()
^^^^
"walk"
next prev parent reply other threads:[~2018-07-10 23:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 7:11 [PATCH 0/3] rhashtable: replace rhashtable_walk_peek implementation NeilBrown
2018-07-06 7:11 ` [PATCH 3/3] rhashtable: implement rhashtable_walk_peek() using rhashtable_walk_last_seen() NeilBrown
2018-07-06 7:11 ` [PATCH 1/3] rhashtable: further improve stability of rhashtable_walk NeilBrown
2018-07-06 8:24 ` kbuild test robot
2018-07-06 9:50 ` NeilBrown
2018-07-06 8:59 ` Paolo Abeni
2018-07-06 9:55 ` NeilBrown
2018-07-06 10:12 ` Paolo Abeni
2018-07-06 9:25 ` kbuild test robot
2018-12-05 3:51 ` [PATCH net-next] " NeilBrown
2018-12-07 5:39 ` Herbert Xu
2018-12-09 22:50 ` NeilBrown
2018-12-11 5:17 ` Herbert Xu
2018-12-12 0:02 ` NeilBrown
2018-12-12 5:46 ` Herbert Xu
2018-12-12 6:41 ` NeilBrown
2018-12-12 8:00 ` Herbert Xu
2018-12-12 8:49 ` NeilBrown
2018-12-13 1:43 ` Herbert Xu
2018-12-13 3:48 ` NeilBrown
2018-12-13 8:47 ` Herbert Xu
2018-07-06 7:11 ` [PATCH 2/3] rhashtable: add rhashtable_walk_last_seen() NeilBrown
2018-07-10 23:55 ` David Miller [this message]
2018-07-15 23:58 ` NeilBrown
2018-07-10 23:55 ` [PATCH 0/3] rhashtable: replace rhashtable_walk_peek implementation 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=20180710.165547.1599531889181336348.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=tom@quantonium.net \
/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).