From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Guillaume Nault <gnault@redhat.com>,
David Miller <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Ido Schimmel <idosch@nvidia.com>,
bpf@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] ipv4: Prepare bpf helpers to .flowi4_tos conversion.
Date: Mon, 11 Nov 2024 19:04:47 -0800 [thread overview]
Message-ID: <20241111190447.43d6c542@kernel.org> (raw)
In-Reply-To: <cover.1731064982.git.gnault@redhat.com>
On Fri, 8 Nov 2024 17:47:09 +0100 Guillaume Nault wrote:
> Continue the process of making a dscp_t variable available when setting
> .flowi4_tos. This series focuses on the BPF helpers that initialise a
> struct flowi4 manually.
>
> The objective is to eventually convert .flowi4_tos to dscp_t, (to get
> type annotation and prevent ECN bits from interfering with DSCP).
Daniel, feel free to take this or we can take with your ack..
next prev parent reply other threads:[~2024-11-12 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 16:47 [PATCH net-next 0/2] ipv4: Prepare bpf helpers to .flowi4_tos conversion Guillaume Nault
2024-11-08 16:47 ` [PATCH net-next 1/2] bpf: ipv4: Prepare __bpf_redirect_neigh_v4() to future " Guillaume Nault
2024-11-10 14:21 ` Ido Schimmel
2024-11-08 16:47 ` [PATCH net-next 2/2] bpf: lwtunnel: Prepare bpf_lwt_xmit_reroute() " Guillaume Nault
2024-11-10 14:22 ` Ido Schimmel
2024-11-12 3:04 ` Jakub Kicinski [this message]
2024-11-15 3:30 ` [PATCH net-next 0/2] ipv4: Prepare bpf helpers to " patchwork-bot+netdevbpf
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=20241111190447.43d6c542@kernel.org \
--to=kuba@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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).