From: Florian Westphal <fw@strlen.de>
To: Julian Anastasov <ja@ssi.bg>
Cc: Simon Horman <horms@verge.net.au>,
Pablo Neira Ayuso <pablo@netfilter.org>,
lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org,
Dust Li <dust.li@linux.alibaba.com>,
Jiejian Wu <jiejian@linux.alibaba.com>,
rcu@vger.kernel.org
Subject: Re: [PATCH nf-next 2/5] ipvs: add resizable hash tables
Date: Sun, 1 Mar 2026 14:23:51 +0100 [thread overview]
Message-ID: <aaQ955aj9ONBe695@strlen.de> (raw)
In-Reply-To: <20260226195021.64943-3-ja@ssi.bg>
Julian Anastasov <ja@ssi.bg> wrote:
> +/**
> + * ip_vs_rht_for_bucket_retry() - Retry bucket if entries are moved
> + * @t: current table, used as cursor, struct ip_vs_rht *var
> + * @bucket: index of current bucket or hash key
> + * @sc: temp seqcount_t *var
> + * @retry: temp int var
> + */
> +#define ip_vs_rht_for_bucket_retry(t, bucket, sc, seq, retry) \
This triggers a small kdoc warning:
Warning: include/net/ip_vs.h:554 function parameter 'seq' not described in 'ip_vs_rht_for_bucket_retry'
next prev parent reply other threads:[~2026-03-01 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 19:50 [PATCH nf-next 0/5] IPVS changes, part 3 of 4 - per-net tables Julian Anastasov
2026-02-26 19:50 ` [PATCH nf-next 1/5] rculist_bl: add hlist_bl_for_each_entry_continue_rcu Julian Anastasov
2026-02-26 19:50 ` [PATCH nf-next 2/5] ipvs: add resizable hash tables Julian Anastasov
2026-03-01 13:23 ` Florian Westphal [this message]
2026-03-02 17:41 ` Julian Anastasov
2026-03-02 19:17 ` Florian Westphal
2026-03-02 22:18 ` Julian Anastasov
2026-03-03 20:27 ` Florian Westphal
2026-02-26 19:50 ` [PATCH nf-next 3/5] ipvs: use resizable hash table for services Julian Anastasov
2026-02-26 19:50 ` [PATCH nf-next 4/5] ipvs: switch to per-net connection table Julian Anastasov
2026-02-26 19:50 ` [PATCH nf-next 5/5] ipvs: use more keys for connection hashing 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=aaQ955aj9ONBe695@strlen.de \
--to=fw@strlen.de \
--cc=dust.li@linux.alibaba.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=jiejian@linux.alibaba.com \
--cc=lvs-devel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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