DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
	Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
	dev@dpdk.org
Cc: indranil@chelsio.com, nirranjan@chelsio.com
Subject: Re: [dpdk-dev] [PATCH] ethdev: add action to swap source and destination MAC to flow API
Date: Thu, 4 Oct 2018 16:36:43 +0100	[thread overview]
Message-ID: <f32dc351-7416-e188-1507-da51339139d7@intel.com> (raw)
In-Reply-To: <569a7ac3-b725-0607-c3c7-4a8656e3d687@solarflare.com>

On 9/24/2018 9:32 AM, Andrew Rybchenko wrote:
> On 9/24/18 11:29 AM, wrote:
>> This action is useful for offloading loopback mode, where the hardware
>> will swap source and destination MAC addresses in the outermost Ethernet
>> header before looping back the packet. This action can be used in
>> conjunction with other rewrite actions to achieve MAC layer transparent
>> NAT where the MAC addresses are swapped before either the source or
>> destination MAC address is rewritten and NAT is performed.
>>
>> Must be used with a valid RTE_FLOW_ITEM_TYPE_ETH flow pattern item.
>> Otherwise, RTE_FLOW_ERROR_TYPE_ACTION error should be returned by the
>> PMDs.
>>
>> Original work by Shagun Agrawal
>>
>> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
> 
> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>

Same here, can you please rebase the patch and keep the ack?

  reply	other threads:[~2018-10-04 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  8:29 Rahul Lakkireddy
2018-09-24  8:32 ` Andrew Rybchenko
2018-10-04 15:36   ` Ferruh Yigit [this message]
2018-10-06 15:45 ` [dpdk-dev] [PATCH v2] " Rahul Lakkireddy
2018-10-09 13:05   ` Ferruh Yigit
2018-10-09 14:49 ` [dpdk-dev] [PATCH] " Ferruh Yigit
2018-10-09 18:34   ` Rahul Lakkireddy

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=f32dc351-7416-e188-1507-da51339139d7@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=indranil@chelsio.com \
    --cc=nirranjan@chelsio.com \
    --cc=rahul.lakkireddy@chelsio.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).