From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>,
"Su, Simei" <simei.su@intel.com>,
"Wu, Wenjun1" <wenjun1.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] net/e1000: report VLAN extend capability for 82576
Date: Wed, 17 May 2023 02:35:05 +0000 [thread overview]
Message-ID: <DM4PR11MB5994BC864ED2610095A25A51D77E9@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230414114638.63590-1-akihiko.odaki@daynix.com>
> -----Original Message-----
> From: Akihiko Odaki <akihiko.odaki@daynix.com>
> Sent: Friday, April 14, 2023 7:47 PM
> To: Su, Simei <simei.su@intel.com>; Wu, Wenjun1 <wenjun1.wu@intel.com>
> Cc: dev@dpdk.org; Akihiko Odaki <akihiko.odaki@daynix.com>
> Subject: [PATCH] net/e1000: report VLAN extend capability for 82576
>
> 82576 also has exended VLAN support.
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> drivers/net/e1000/igb_rxtx.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/e1000/igb_rxtx.c b/drivers/net/e1000/igb_rxtx.c index
> f32dee46df..25ad9eb4e5 100644
> --- a/drivers/net/e1000/igb_rxtx.c
> +++ b/drivers/net/e1000/igb_rxtx.c
> @@ -1648,7 +1648,8 @@ igb_get_rx_port_offloads_capa(struct rte_eth_dev
> *dev)
> RTE_ETH_RX_OFFLOAD_SCATTER |
> RTE_ETH_RX_OFFLOAD_RSS_HASH;
>
> - if (hw->mac.type == e1000_i350 ||
> + if (hw->mac.type == e1000_82576 ||
> + hw->mac.type == e1000_i350 ||
> hw->mac.type == e1000_i210 ||
> hw->mac.type == e1000_i211)
> rx_offload_capa |= RTE_ETH_RX_OFFLOAD_VLAN_EXTEND;
> --
> 2.40.0
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2023-05-17 2:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 11:46 Akihiko Odaki
2023-05-17 2:35 ` Zhang, Qi Z [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=DM4PR11MB5994BC864ED2610095A25A51D77E9@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=akihiko.odaki@daynix.com \
--cc=dev@dpdk.org \
--cc=simei.su@intel.com \
--cc=wenjun1.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).