From: Guillaume Nault <gnault@redhat.com>
To: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: [PATCH net-next 0/5] ipv4: Convert ip_route_input_slow() and its callers to dscp_t.
Date: Tue, 1 Oct 2024 21:28:30 +0200 [thread overview]
Message-ID: <cover.1727807926.git.gnault@redhat.com> (raw)
Prepare ip_route_input_slow() and its call chain to future conversion
of ->flowi4_tos.
The ->flowi4_tos field of "struct flowi4" is used in many different
places, which makes it hard to convert it from __u8 to dscp_t.
In order to avoid a big patch updating all its users at once, this
patch series gradually converts some users to dscp_t. Those users now
set ->flowi4_tos from a dscp_t variable that is converted to __u8 using
inet_dscp_to_dsfield().
When all users of ->flowi4_tos will use a dscp_t variable, converting
that field to dscp_t will just be a matter of removing all the
inet_dscp_to_dsfield() conversions.
This series concentrates on ip_route_input_slow() and its direct and
indirect callers.
Guillaume Nault (5):
ipv4: Convert icmp_route_lookup() to dscp_t.
ipv4: Convert ip_route_input() to dscp_t.
ipv4: Convert ip_route_input_noref() to dscp_t.
ipv4: Convert ip_route_input_rcu() to dscp_t.
ipv4: Convert ip_route_input_slow() to dscp_t.
drivers/net/ipvlan/ipvlan_l3s.c | 6 ++++--
include/net/ip.h | 5 +++++
include/net/route.h | 8 ++++----
net/bridge/br_netfilter_hooks.c | 8 +++++---
net/core/lwt_bpf.c | 5 +++--
net/ipv4/icmp.c | 19 +++++++++----------
net/ipv4/ip_fragment.c | 4 ++--
net/ipv4/ip_input.c | 2 +-
net/ipv4/ip_options.c | 3 ++-
net/ipv4/route.c | 32 ++++++++++++++++++--------------
net/ipv4/xfrm4_input.c | 2 +-
net/ipv4/xfrm4_protocol.c | 2 +-
net/ipv6/ip6_tunnel.c | 4 ++--
13 files changed, 57 insertions(+), 43 deletions(-)
--
2.39.2
next reply other threads:[~2024-10-01 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:28 Guillaume Nault [this message]
2024-10-01 19:28 ` [PATCH net-next 1/5] ipv4: Convert icmp_route_lookup() to dscp_t Guillaume Nault
2024-10-01 19:28 ` [PATCH net-next 2/5] ipv4: Convert ip_route_input() " Guillaume Nault
2024-10-01 19:28 ` [PATCH net-next 3/5] ipv4: Convert ip_route_input_noref() " Guillaume Nault
2024-10-01 19:28 ` [PATCH net-next 4/5] ipv4: Convert ip_route_input_rcu() " Guillaume Nault
2024-10-01 19:29 ` [PATCH net-next 5/5] ipv4: Convert ip_route_input_slow() " Guillaume Nault
2024-10-02 2:45 ` [PATCH net-next 0/5] ipv4: Convert ip_route_input_slow() and its callers " David Ahern
2024-10-03 23:40 ` 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=cover.1727807926.git.gnault@redhat.com \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=idosch@nvidia.com \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--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).