From: Ido Schimmel <idosch@nvidia.com>
To: Guillaume Nault <gnault@redhat.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>
Subject: Re: [PATCH net-next 1/4] ipv4: Prepare fib_compute_spec_dst() to future .flowi4_tos conversion.
Date: Tue, 22 Oct 2024 15:35:20 +0300 [thread overview]
Message-ID: <ZxecCBlEvmcMxODJ@shredder.mtl.com> (raw)
In-Reply-To: <a0eba69cce94f747e4c7516184a85ffd0abbe3f0.1729530028.git.gnault@redhat.com>
On Tue, Oct 22, 2024 at 11:48:00AM +0200, Guillaume Nault wrote:
> Use ip4h_dscp() to get the DSCP from the IPv4 header, then convert the
> dscp_t value to __u8 with inet_dscp_to_dsfield().
>
> Then, when we'll convert .flowi4_tos to dscp_t, we'll just have to drop
> the inet_dscp_to_dsfield() call.
>
> Signed-off-by: Guillaume Nault <gnault@redhat.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2024-10-22 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 9:47 [PATCH net-next 0/4] ipv4: Prepare core ipv4 files to future .flowi4_tos conversion Guillaume Nault
2024-10-22 9:48 ` [PATCH net-next 1/4] ipv4: Prepare fib_compute_spec_dst() " Guillaume Nault
2024-10-22 12:35 ` Ido Schimmel [this message]
2024-10-22 9:48 ` [PATCH net-next 2/4] ipv4: Prepare icmp_reply() " Guillaume Nault
2024-10-22 12:36 ` Ido Schimmel
2024-10-22 9:48 ` [PATCH net-next 3/4] ipv4: Prepare ipmr_rt_fib_lookup() " Guillaume Nault
2024-10-22 12:37 ` Ido Schimmel
2024-10-22 9:48 ` [PATCH net-next 4/4] ipv4: Prepare ip_rt_get_source() " Guillaume Nault
2024-10-22 12:37 ` Ido Schimmel
2024-10-29 18:50 ` [PATCH net-next 0/4] ipv4: Prepare core ipv4 files " 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=ZxecCBlEvmcMxODJ@shredder.mtl.com \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.