From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <lmb@isovalent.com>
Cc: <andrii@kernel.org>, <ast@kernel.org>, <bpf@vger.kernel.org>,
<daniel@iogearbox.net>, <davem@davemloft.net>,
<dsahern@kernel.org>, <edumazet@google.com>, <haoluo@google.com>,
<hemanthmalla@gmail.com>, <joe@wand.net.nz>,
<john.fastabend@gmail.com>, <jolsa@kernel.org>,
<kpsingh@kernel.org>, <kuba@kernel.org>, <kuniyu@amazon.com>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<martin.lau@linux.dev>, <mykolal@fb.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>, <sdf@google.com>,
<shuah@kernel.org>, <song@kernel.org>,
<willemdebruijn.kernel@gmail.com>, <yhs@fb.com>
Subject: Re: [PATCH bpf-next v4 2/7] net: export inet_lookup_reuseport and inet6_lookup_reuseport
Date: Wed, 28 Jun 2023 10:43:29 -0700 [thread overview]
Message-ID: <20230628174329.68454-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20230613-so-reuseport-v4-2-4ece76708bba@isovalent.com>
From: Lorenz Bauer <lmb@isovalent.com>
Date: Wed, 28 Jun 2023 10:48:17 +0100
> Rename the existing reuseport helpers for IPv4 and IPv6 so that they
> can be invoked in the follow up commit. Export them so that building
> DCCP and IPv6 as a module works.
>
> No change in functionality.
>
> Signed-off-by: Lorenz Bauer <lmb@isovalent.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
next prev parent reply other threads:[~2023-06-28 17:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:48 [PATCH bpf-next v4 0/7] Add SO_REUSEPORT support for TC bpf_sk_assign Lorenz Bauer
2023-06-28 9:48 ` [PATCH bpf-next v4 1/7] udp: re-score reuseport groups when connected sockets are present Lorenz Bauer
2023-06-28 9:48 ` [PATCH bpf-next v4 2/7] net: export inet_lookup_reuseport and inet6_lookup_reuseport Lorenz Bauer
2023-06-28 17:43 ` Kuniyuki Iwashima [this message]
2023-06-28 9:48 ` [PATCH bpf-next v4 3/7] net: remove duplicate reuseport_lookup functions Lorenz Bauer
2023-06-28 18:32 ` Kuniyuki Iwashima
2023-07-03 9:45 ` Lorenz Bauer
2023-06-28 9:48 ` [PATCH bpf-next v4 4/7] net: document inet[6]_lookup_reuseport sk_state requirements Lorenz Bauer
2023-06-28 18:39 ` Kuniyuki Iwashima
2023-06-28 9:48 ` [PATCH bpf-next v4 5/7] net: remove duplicate sk_lookup helpers Lorenz Bauer
2023-06-28 9:48 ` [PATCH bpf-next v4 6/7] bpf, net: Support SO_REUSEPORT sockets with bpf_sk_assign Lorenz Bauer
2023-06-28 18:50 ` Kuniyuki Iwashima
2023-07-03 9:53 ` Lorenz Bauer
2023-06-28 18:53 ` Kuniyuki Iwashima
2023-07-03 9:57 ` Lorenz Bauer
2023-07-06 0:40 ` Kuniyuki Iwashima
2023-07-06 8:11 ` Lorenz Bauer
2023-07-06 15:33 ` Kuniyuki Iwashima
2023-07-11 0:41 ` Alexei Starovoitov
2023-06-28 9:48 ` [PATCH bpf-next v4 7/7] selftests/bpf: Test that SO_REUSEPORT can be used with sk_assign helper Lorenz Bauer
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=20230628174329.68454-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=hemanthmalla@gmail.com \
--cc=joe@wand.net.nz \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lmb@isovalent.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yhs@fb.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