From: Nikolay Aleksandrov <razor@blackwall.org>
To: Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Cc: petrm@nvidia.com, mlxsw@nvidia.com, edumazet@google.com,
roopa@nvidia.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next 06/11] vxlan: Expose vxlan_xmit_one()
Date: Tue, 14 Mar 2023 13:52:30 +0200 [thread overview]
Message-ID: <2097d3df-050e-ad7a-66dd-93019365b19d@blackwall.org> (raw)
In-Reply-To: <20230313145349.3557231-7-idosch@nvidia.com>
On 13/03/2023 16:53, Ido Schimmel wrote:
> Given a packet and a remote destination, the function will take care of
> encapsulating the packet and transmitting it to the destination.
>
> Expose it so that it could be used in subsequent patches by the MDB code
> to transmit a packet to the remote destination(s) stored in the MDB
> entry.
>
> It will allow us to keep the MDB code self-contained, not exposing its
> data structures to the rest of the VXLAN driver.
>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
> drivers/net/vxlan/vxlan_core.c | 5 ++---
> drivers/net/vxlan/vxlan_private.h | 2 ++
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2023-03-14 11:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 14:53 [Bridge] [PATCH net-next 00/11] vxlan: Add MDB support Ido Schimmel
2023-03-13 14:53 ` [Bridge] [PATCH net-next 01/11] net: Add MDB net device operations Ido Schimmel
2023-03-14 11:41 ` Nikolay Aleksandrov
2023-03-13 14:53 ` [Bridge] [PATCH net-next 02/11] bridge: mcast: Implement " Ido Schimmel
2023-03-14 11:43 ` Nikolay Aleksandrov
2023-03-13 14:53 ` [Bridge] [PATCH net-next 03/11] rtnetlink: bridge: mcast: Move MDB handlers out of bridge driver Ido Schimmel
2023-03-14 11:51 ` Nikolay Aleksandrov
2023-03-13 14:53 ` [Bridge] [PATCH net-next 04/11] rtnetlink: bridge: mcast: Relax group address validation in common code Ido Schimmel
2023-03-14 11:51 ` Nikolay Aleksandrov
2023-03-13 14:53 ` [Bridge] [PATCH net-next 05/11] vxlan: Move address helpers to private headers Ido Schimmel
2023-03-14 11:52 ` Nikolay Aleksandrov
2023-03-13 14:53 ` [Bridge] [PATCH net-next 06/11] vxlan: Expose vxlan_xmit_one() Ido Schimmel
2023-03-14 11:52 ` Nikolay Aleksandrov [this message]
2023-03-13 14:53 ` [Bridge] [PATCH net-next 07/11] vxlan: mdb: Add MDB control path support Ido Schimmel
2023-03-14 12:24 ` Nikolay Aleksandrov
2023-03-13 14:53 ` [Bridge] [PATCH net-next 08/11] vxlan: mdb: Add an internal flag to indicate MDB usage Ido Schimmel
2023-03-14 12:24 ` Nikolay Aleksandrov
2023-03-13 14:53 ` [Bridge] [PATCH net-next 09/11] vxlan: Add MDB data path support Ido Schimmel
2023-03-14 12:35 ` Nikolay Aleksandrov
2023-03-15 7:58 ` Ido Schimmel
2023-03-13 14:53 ` [Bridge] [PATCH net-next 10/11] vxlan: Enable MDB support Ido Schimmel
2023-03-14 12:35 ` Nikolay Aleksandrov
2023-03-13 14:53 ` [Bridge] [PATCH net-next 11/11] selftests: net: Add VXLAN MDB test Ido Schimmel
2023-03-14 12:35 ` Nikolay Aleksandrov
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=2097d3df-050e-ad7a-66dd-93019365b19d@blackwall.org \
--to=razor@blackwall.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=roopa@nvidia.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