From: patchwork-bot+netdevbpf@kernel.org
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
greearb@candelatech.com
Subject: Re: [PATCH net-next] net: Add l3mdev index to flow struct and avoid oif reset for port devices
Date: Wed, 16 Mar 2022 05:00:10 +0000 [thread overview]
Message-ID: <164740681044.10029.16814487037983806451.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220314204551.16369-1-dsahern@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Mar 2022 14:45:51 -0600 you wrote:
> The fundamental premise of VRF and l3mdev core code is binding a socket
> to a device (l3mdev or netdev with an L3 domain) to indicate L3 scope.
> Legacy code resets flowi_oif to the l3mdev losing any original port
> device binding. Ben (among others) has demonstrated use cases where the
> original port device binding is important and needs to be retained.
> This patch handles that by adding a new entry to the common flow struct
> that can indicate the l3mdev index for later rule and table matching
> avoiding the need to reset flowi_oif.
>
> [...]
Here is the summary with links:
- [net-next] net: Add l3mdev index to flow struct and avoid oif reset for port devices
https://git.kernel.org/netdev/net-next/c/40867d74c374
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-03-16 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 20:45 [PATCH net-next] net: Add l3mdev index to flow struct and avoid oif reset for port devices David Ahern
2022-03-16 5:00 ` patchwork-bot+netdevbpf [this message]
2022-03-22 9:22 ` Ido Schimmel
2022-03-22 14:26 ` David Ahern
2022-03-22 15:31 ` Ido Schimmel
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=164740681044.10029.16814487037983806451.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=greearb@candelatech.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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.