DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Moti Haimovsky <motih@mellanox.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx4: fix Rx packet type offloads
Date: Thu, 9 Nov 2017 18:32:41 -0800	[thread overview]
Message-ID: <8c6b760a-9752-1213-8fe9-ff2cacb5263b@intel.com> (raw)
In-Reply-To: <20171109091831.GY24849@6wind.com>

On 11/9/2017 1:18 AM, Adrien Mazarguil wrote:
> On Thu, Nov 09, 2017 at 10:59:33AM +0200, Moti Haimovsky wrote:
>> This patch improves Rx packet type offload report in case the device is
>> a virtual function device.
>> In these devices we observed that the L2 tunnel flag is set also for
>> non-tunneled packets, this leads to a complete misinterpretation of the
>> packet type being received.
>> This issue occurs since the tunnel_mode is not set to 0x7 by the driver
>> for virtual devices and therefore the value in the L2 tunnel flag is
>> meaningless and should be ignored.
>>
>> Fixes: aee4a03fee4f ("net/mlx4: enhance Rx packet type offloads")
>>
>> Signed-off-by: Moti Haimovsky <motih@mellanox.com>
> 
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

Applied to dpdk/master, thanks.

      reply	other threads:[~2017-11-10  2:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 18:47 [dpdk-dev] [PATCH v2] net/mlx4: improve Rx packet type offloads report Moti Haimovsky
2017-11-08 19:56 ` Thomas Monjalon
2017-11-09  8:59 ` [dpdk-dev] [PATCH v3] net/mlx4: fix Rx packet type offloads Moti Haimovsky
2017-11-09  9:18   ` Adrien Mazarguil
2017-11-10  2:32     ` Ferruh Yigit [this message]

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=8c6b760a-9752-1213-8fe9-ff2cacb5263b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=motih@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).