From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Chen, LingliX" <linglix.chen@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Chen, LingliX" <linglix.chen@intel.com>
Subject: Re: [dts] [PATCH V1 0/2] modify igb and igc nic pktsize
Date: Tue, 25 May 2021 05:38:19 +0000 [thread overview]
Message-ID: <5621fa2124a5449eb23c9d13bac854b5@intel.com> (raw)
In-Reply-To: <20210430154813.15699-1-linglix.chen@intel.com>
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Lingli Chen
> Sent: 2021年4月30日 23:48
> To: dts@dpdk.org
> Cc: Chen, LingliX <linglix.chen@intel.com>
> Subject: [dts] [PATCH V1 0/2] modify igb and igc nic pktsize
>
> 1.According to dpdk commit ddbc8c16a97f ("net/e1000: fix max Rx packet size"):
> modify shutdown_api/enable_disablejumbo igb pktSize.
> 2.According to dpdk-26436:If LPE is 1b,the maximum packet size that Foxville
> can receive is defined in the RLPML.RLPML register.The RLPML.RLPML register
> was set to MTU + 14 + 4 bytes (must consider at lease 1 VLAN tag since VLAN
> tag is not included in MTU).
> modify tests/mtu_update igb and igc critical values.
>
> Lingli Chen (2):
> tests/mtu_update: modify igb and igc critical values
> tests/shutdown_api: modify igb pktSize
>
> tests/TestSuite_mtu_update.py | 19 +++++++++++++------
> tests/TestSuite_shutdown_api.py | 4 ++--
> 2 files changed, 15 insertions(+), 8 deletions(-)
>
> --
> 2.17.1
Applied, please mind your length of commit message, it should be less than 74.
prev parent reply other threads:[~2021-05-25 5:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 15:48 Lingli Chen
2021-04-30 7:18 ` Chen, LingliX
2021-04-30 15:48 ` [dts] [PATCH V1 1/2] tests/mtu_update: modify igb and igc critical values Lingli Chen
2021-04-30 15:48 ` [dts] [PATCH V1 2/2] tests/shutdown_api: modify igb pktSize Lingli Chen
2021-05-25 5:38 ` Tu, Lijuan [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=5621fa2124a5449eb23c9d13bac854b5@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=linglix.chen@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).