From: Julian Anastasov <ja@ssi.bg>
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org, "Paul E . McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, Dust Li <dust.li@linux.alibaba.com>,
Jiejian Wu <jiejian@linux.alibaba.com>,
Jiri Wiesner <jwiesner@suse.de>
Subject: [PATCH RFC net-next 01/14] rculist_bl: add hlist_bl_for_each_entry_continue_rcu
Date: Tue, 15 Aug 2023 20:30:18 +0300 [thread overview]
Message-ID: <20230815173031.168344-2-ja@ssi.bg> (raw)
In-Reply-To: <20230815173031.168344-1-ja@ssi.bg>
Add hlist_bl_for_each_entry_continue_rcu and hlist_bl_next_rcu
Signed-off-by: Julian Anastasov <ja@ssi.bg>
---
include/linux/rculist_bl.h | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/include/linux/rculist_bl.h b/include/linux/rculist_bl.h
index 0b952d06eb0b..93a757793d83 100644
--- a/include/linux/rculist_bl.h
+++ b/include/linux/rculist_bl.h
@@ -24,6 +24,10 @@ static inline struct hlist_bl_node *hlist_bl_first_rcu(struct hlist_bl_head *h)
((unsigned long)rcu_dereference_check(h->first, hlist_bl_is_locked(h)) & ~LIST_BL_LOCKMASK);
}
+/* return the next element in an RCU protected list */
+#define hlist_bl_next_rcu(node) \
+ (*((struct hlist_bl_node __rcu **)(&(node)->next)))
+
/**
* hlist_bl_del_rcu - deletes entry from hash list without re-initialization
* @n: the element to delete from the hash list.
@@ -98,4 +102,17 @@ static inline void hlist_bl_add_head_rcu(struct hlist_bl_node *n,
({ tpos = hlist_bl_entry(pos, typeof(*tpos), member); 1; }); \
pos = rcu_dereference_raw(pos->next))
+/**
+ * hlist_bl_for_each_entry_continue_rcu - iterate over a list continuing after
+ * current point
+ * @tpos: the type * to use as a loop cursor.
+ * @pos: the &struct hlist_bl_node to use as a loop cursor.
+ * @member: the name of the hlist_bl_node within the struct.
+ */
+#define hlist_bl_for_each_entry_continue_rcu(tpos, pos, member) \
+ for (pos = rcu_dereference_raw(hlist_bl_next_rcu(&(tpos)->member)); \
+ pos && \
+ ({ tpos = hlist_bl_entry(pos, typeof(*tpos), member); 1; }); \
+ pos = rcu_dereference_raw(hlist_bl_next_rcu(pos)))
+
#endif
--
2.41.0
next prev parent reply other threads:[~2023-08-15 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 17:30 [PATCH RFC net-next 00/14] ipvs: per-net tables and optimizations Julian Anastasov
2023-08-15 17:30 ` Julian Anastasov [this message]
2023-08-15 18:39 ` [PATCH RFC net-next 01/14] rculist_bl: add hlist_bl_for_each_entry_continue_rcu Paul E. McKenney
2023-08-16 16:02 ` Julian Anastasov
2023-08-16 22:54 ` Paul E. McKenney
2023-08-15 17:30 ` [PATCH RFC net-next 02/14] ipvs: make ip_vs_svc_table and ip_vs_svc_fwm_table per netns Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 03/14] ipvs: some service readers can use RCU Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 04/14] ipvs: use single svc table Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 05/14] ipvs: do not keep dest_dst after dest is removed Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 06/14] ipvs: use more counters to avoid service lookups Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 07/14] ipvs: add resizable hash tables Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 08/14] ipvs: use resizable hash table for services Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 09/14] ipvs: switch to per-net connection table Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 10/14] ipvs: show the current conn_tab size to users Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 11/14] ipvs: no_cport and dropentry counters can be per-net Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 12/14] ipvs: use more keys for connection hashing Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 13/14] ipvs: add ip_vs_status info Julian Anastasov
2023-08-15 17:30 ` [PATCH RFC net-next 14/14] ipvs: add conn_lfactor and svc_lfactor sysctl vars Julian Anastasov
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=20230815173031.168344-2-ja@ssi.bg \
--to=ja@ssi.bg \
--cc=dust.li@linux.alibaba.com \
--cc=horms@verge.net.au \
--cc=jiejian@linux.alibaba.com \
--cc=jwiesner@suse.de \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@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).