From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Xing, Beilei" <beilei.xing@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix missing mbuf fast free offload
Date: Thu, 10 May 2018 23:09:50 +0100 [thread overview]
Message-ID: <658da15d-58ca-dfbd-098b-7bb1b7c486d4@intel.com> (raw)
In-Reply-To: <df08c8c2-0301-d2de-c32f-628cd4d6620a@intel.com>
On 5/8/2018 5:50 PM, Ferruh Yigit wrote:
> On 5/7/2018 6:08 AM, Xing, Beilei wrote:
>>
>>
>>> -----Original Message-----
>>> From: Zhang, Qi Z
>>> Sent: Monday, May 7, 2018 9:26 AM
>>> To: Yigit, Ferruh <ferruh.yigit@intel.com>
>>> Cc: Xing, Beilei <beilei.xing@intel.com>; dev@dpdk.org; Zhang, Qi Z
>>> <qi.z.zhang@intel.com>
>>> Subject: [PATCH] net/i40e: fix missing mbuf fast free offload
>>>
>>> Expose the missing mbuf fast free capability since i40 does support it.
>>>
>>> Fixes: 7497d3e2f777 ("net/i40e: convert to new Tx offloads API")
>>>
>>> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
>
>>
>> Acked-by: Beilei Xing <beilei.xing@intel.com>
>
> Applied to dpdk-next-net/master, thanks.
Hi Beilei, Qi,
This patch is preventing i40e to use Tx avx2 fast path and cause a performance
drop, you need to allow this offload in Tx data path selection logic.
Dropping this patch from next-net, updated patch status in patchwork, please
send a new version.
Thanks,
ferruh
next prev parent reply other threads:[~2018-05-10 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 1:26 Qi Zhang
2018-05-07 5:08 ` Xing, Beilei
2018-05-08 16:50 ` Ferruh Yigit
2018-05-10 22:09 ` Ferruh Yigit [this message]
2018-05-11 0:39 ` Zhang, Qi Z
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=658da15d-58ca-dfbd-098b-7bb1b7c486d4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.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).