From: Jeff Guo <jia.guo@intel.com>
To: zhihongx.peng@intel.com, beilei.xing@intel.com
Cc: dev@dpdk.org, declan.doherty@intel.com
Subject: Re: [dpdk-dev] [DPDK] net/i40e: add the VLAN capabilities of NIC
Date: Mon, 20 Jul 2020 16:56:59 +0800 [thread overview]
Message-ID: <cee43abd-81f1-d794-647c-9ac183b4dd77@intel.com> (raw)
In-Reply-To: <20200720024214.13972-1-zhihongx.peng@intel.com>
hi, zhihong
On 7/20/2020 10:42 AM, zhihongx.peng@intel.com wrote:
> From: Peng Zhihong <zhihongx.peng@intel.com>
>
> The rte_eth_dev_set_vlan_offload function will check whether the NIC has
> the set vlan feature. If it has not, it will return failure. So need
"...has the set vlan feature..." , that need to refine.
> to add all the vlan feature flags of the NIC.
>
> Fixes: e0cb96204b71 (net/i40e: add support for representor ports)
> Cc: declan.doherty@intel.com
>
> Signed-off-by: Peng Zhihong <zhihongx.peng@intel.com>
> ---
> drivers/net/i40e/i40e_vf_representor.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/i40e/i40e_vf_representor.c b/drivers/net/i40e/i40e_vf_representor.c
> index b07b35c03..083bc1a5f 100644
> --- a/drivers/net/i40e/i40e_vf_representor.c
> +++ b/drivers/net/i40e/i40e_vf_representor.c
> @@ -46,7 +46,8 @@ i40e_vf_representor_dev_infos_get(struct rte_eth_dev *ethdev,
> DEV_RX_OFFLOAD_QINQ_STRIP |
> DEV_RX_OFFLOAD_IPV4_CKSUM |
> DEV_RX_OFFLOAD_UDP_CKSUM |
> - DEV_RX_OFFLOAD_TCP_CKSUM;
> + DEV_RX_OFFLOAD_TCP_CKSUM |
> + DEV_RX_OFFLOAD_VLAN_FILTER;
> dev_info->tx_offload_capa =
> DEV_TX_OFFLOAD_MULTI_SEGS |
> DEV_TX_OFFLOAD_VLAN_INSERT |
next prev parent reply other threads:[~2020-07-20 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 2:42 [dpdk-dev] [DPDK] net/i40e: add the VLAN capabilities of NIC zhihongx.peng
2020-07-20 8:56 ` Jeff Guo [this message]
2020-07-21 2:45 ` [dpdk-dev] [DPDK v2] net/i40e: add VLAN filter feature to capability zhihongx.peng
2020-07-21 3:11 ` Jeff Guo
2020-07-21 5:01 ` 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=cee43abd-81f1-d794-647c-9ac183b4dd77@intel.com \
--to=jia.guo@intel.com \
--cc=beilei.xing@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=zhihongx.peng@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).