From: Jack MIN <jackmin@mellanox.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Shahaf Shuler <shahafs@mellanox.com>,
"Xueming(Steven) Li" <xuemingl@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [RFC] ethdev: add generic MAC address rewrite actions
Date: Wed, 29 Aug 2018 11:25:53 +0800 [thread overview]
Message-ID: <20180829032553.cccdkdkiho537fdp@MTBC-JACKMIN.mtl.com> (raw)
In-Reply-To: <1855dea4-7eb7-acf0-d31a-7d8b4b143e0d@solarflare.com>
On Tue, Aug 28, 2018 at 01:15:09PM +0300, Andrew Rybchenko wrote:
> On 08/07/2018 05:20 PM, Jack Min wrote:
> > There is a need to offload rewrite MAC address for both destination and source
> > from the matched flow
> >
> > The proposed actions could make above easily achieved
> >
> >
> > Signed-off-by: Xiaoyu Min <jackmin@mellanox.com<mailto:jackmin@mellanox.com>>
>
> The only question I have is which Ethernet header is edited, if there are
> many
> Ethernet headers in the case of tunnels. I guess the outermost, but it
> should
> be stated in the description.
>
OK. I'll add it in V2.
Thanks
-Jack
next prev parent reply other threads:[~2018-08-29 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 14:20 Jack Min
2018-08-13 10:08 ` Rahul Lakkireddy
2018-08-14 9:15 ` Jack MIN
2018-08-21 8:14 ` Rahul Lakkireddy
2018-08-23 2:15 ` Jack MIN
2018-08-23 8:13 ` Rahul Lakkireddy
2018-08-23 13:58 ` Ferruh Yigit
2018-08-28 10:15 ` Andrew Rybchenko
2018-08-29 3:25 ` Jack MIN [this message]
2018-08-30 6:54 ` [dpdk-dev] [PATCH v2] " Xiaoyu Min
2018-08-30 7:40 ` Jack MIN
2018-08-30 8:00 ` [dpdk-dev] [RFC " Xiaoyu Min
2018-08-31 8:33 ` Andrew Rybchenko
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=20180829032553.cccdkdkiho537fdp@MTBC-JACKMIN.mtl.com \
--to=jackmin@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=xuemingl@mellanox.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).