From: Sabrina Dubroca <sd@queasysnail.net>
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH iproute2-next] ip-xfrm: add pcpu-num support
Date: Tue, 4 Nov 2025 14:27:22 +0100 [thread overview]
Message-ID: <aQn_Om--BOEkVKBL@krikkit> (raw)
In-Reply-To: <cb6455d7-a6d5-4a1d-940e-31cb9a4fc486@kernel.org>
2025-11-03, 09:47:09 -0700, David Ahern wrote:
> On 10/29/25 5:06 AM, Sabrina Dubroca wrote:
> > The kernel supports passing the XFRMA_SA_PCPU attribute when creating
> > a state (via NEWSA or ALLOCSPI). Add a "pcpu-num" argument, and print
> > XFRMA_SA_PCPU when the kernel provides it.
> >
> > Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
> > ---
> > ip/ipxfrm.c | 6 ++++++
> > ip/xfrm_state.c | 20 ++++++++++++++++++--
> > man/man8/ip-xfrm.8 | 4 ++++
> > 3 files changed, 28 insertions(+), 2 deletions(-)
> >
>
> ...
>
> > @@ -309,6 +309,7 @@ static int xfrm_state_modify(int cmd, unsigned int flags, int argc, char **argv)
> > bool is_if_id_set = false;
> > __u32 if_id = 0;
> > __u32 tfcpad = 0;
> > + __u32 pcpu_num = -1;
> >
> > while (argc > 0) {
> > if (strcmp(*argv, "mode") == 0) {
>
> ...
>
> > @@ -797,6 +805,7 @@ static int xfrm_state_allocspi(int argc, char **argv)
> > struct xfrm_mark mark = {0, 0};
> > struct nlmsghdr *answer;
> > __u8 dir = 0;
> > + __u32 pcpu_num = -1;
>
>
> iproute2 follows net-next with reverse xmas tree ordering. I realize
> that is a bit hard for some of the code -- like ipxfrm.c.
Right, it wasn't obvious just looking at those functions in isolation.
> I fixed up these 2 to that ordering at least in the local scope and
> applied to iproute2-next
Thanks!
--
Sabrina
prev parent reply other threads:[~2025-11-04 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 11:06 [PATCH iproute2-next] ip-xfrm: add pcpu-num support Sabrina Dubroca
2025-10-30 16:06 ` Stephen Hemminger
2025-10-30 23:51 ` Sabrina Dubroca
2025-10-31 1:32 ` David Ahern
2025-11-03 9:48 ` Sabrina Dubroca
2025-11-03 16:36 ` David Ahern
2025-11-04 13:06 ` Sabrina Dubroca
2025-11-03 16:47 ` David Ahern
2025-11-04 13:27 ` Sabrina Dubroca [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=aQn_Om--BOEkVKBL@krikkit \
--to=sd@queasysnail.net \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).