From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wu, Yanglong" <yanglong.wu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dai, Wei" <wei.dai@intel.com>, "Yao, Lei A" <lei.a.yao@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: fix I40e start failing for missing JUMBO_FRAME offload
Date: Wed, 18 Apr 2018 12:16:34 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115319FBCA@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180418014204.56785-1-yanglong.wu@intel.com>
> -----Original Message-----
> From: Wu, Yanglong
> Sent: Wednesday, April 18, 2018 9:42 AM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Dai, Wei <wei.dai@intel.com>; Yao,
> Lei A <lei.a.yao@intel.com>; Wu, Yanglong <yanglong.wu@intel.com>
> Subject: [PATCH v2] net/i40e: fix I40e start failing for missing JUMBO_FRAME
> offload
>
> JUMBO_FRAME offload should be set as default, missing it will lead to start
> failing for I40e.
>
> Fixes: fbf959fe61e7 ("net/i40e: convert to new Rx offloads API")
> Signed-off-by: Yanglong Wu <yanglong.wu@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Title and commit log could be changed to
net/i40e: fix missing jumbo frame offload capability
JUMBO_FRAME offload capability should be exposed since i40e
does support it.
next prev parent reply other threads:[~2018-04-18 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 7:28 [dpdk-dev] [PATCH] " Yanglong Wu
2018-04-17 10:38 ` Zhang, Qi Z
2018-04-18 1:42 ` [dpdk-dev] [PATCH v2] " Yanglong Wu
2018-04-18 12:16 ` Zhang, Qi Z [this message]
2018-04-19 2:10 ` [dpdk-dev] [PATCH] " Yanglong Wu
2018-04-19 2:19 ` [dpdk-dev] [PATCH v3] net/i40e:fix missing jumbo frame offload capability Yanglong Wu
2018-04-27 7:27 ` Zhang, Helin
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=039ED4275CED7440929022BC67E706115319FBCA@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=lei.a.yao@intel.com \
--cc=wei.dai@intel.com \
--cc=yanglong.wu@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).