From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>, "Guo, Jia" <jia.guo@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/e1000: fix max Rx packet size
Date: Fri, 9 Apr 2021 00:58:43 +0000 [thread overview]
Message-ID: <BN8PR11MB379569E2261863F35CC7EAB4F7739@BN8PR11MB3795.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210408074102.15480-1-alvinx.zhang@intel.com>
> -----Original Message-----
> From: Zhang, AlvinX <alvinx.zhang@intel.com>
> Sent: Thursday, April 8, 2021 15:41
> To: Wang, Haiyue <haiyue.wang@intel.com>; Guo, Jia <jia.guo@intel.com>
> Cc: dev@dpdk.org; Zhang, AlvinX <alvinx.zhang@intel.com>; stable@dpdk.org
> Subject: [PATCH v2] net/e1000: fix max Rx packet size
>
> According to E1000_ETH_OVERHEAD definition, max_rx_pkt_len contains
> one VLAN tag size. Therefore when config RLPML register, if dual VLAN
> not enabled there is no need to add VLAN tag size to max_rx_pkt_len,
> otherwise only one another VLAN tag size should be added to.
>
> Fixes: e51abef39382 ("igb: fix max RX packet size and support dual VLAN")
> Cc: stable@dpdk.org
>
> Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>
> ---
>
> V2: Update commit log
> ---
> drivers/net/e1000/igb_ethdev.c | 5 ++---
> drivers/net/e1000/igb_rxtx.c | 9 ++++++---
> 2 files changed, 8 insertions(+), 6 deletions(-)
>
Acked-by: Haiyue Wang <haiyue.wang@intel.com>
> 1.8.3.1
next prev parent reply other threads:[~2021-04-09 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 7:29 [dpdk-dev] [PATCH] " Alvin Zhang
2021-04-08 7:41 ` [dpdk-dev] [PATCH v2] " Alvin Zhang
2021-04-08 9:51 ` Chen, LingliX
2021-04-09 0:58 ` Wang, Haiyue [this message]
2021-04-13 5:25 ` 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=BN8PR11MB379569E2261863F35CC7EAB4F7739@BN8PR11MB3795.namprd11.prod.outlook.com \
--to=haiyue.wang@intel.com \
--cc=alvinx.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.com \
--cc=stable@dpdk.org \
/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).