From: "Peng, Yuan" <yuan.peng@intel.com>
To: "Li, WeiyuanX" <weiyuanx.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: RE: [dts][PATCH V1 1/2] tests/smoke_base modify ixgbe support vf jumbo verify.
Date: Tue, 10 May 2022 03:31:01 +0000 [thread overview]
Message-ID: <CO1PR11MB50580433C7EDD1D7B1F60E9DFEC99@CO1PR11MB5058.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220509074639.4135273-1-weiyuanx.li@intel.com>
Acked-by: Peng, Yuan <yuan.peng@intel.com>
-----Original Message-----
From: Li, WeiyuanX <weiyuanx.li@intel.com>
Sent: Monday, May 9, 2022 3:47 PM
To: dts@dpdk.org; Peng, Yuan <yuan.peng@intel.com>
Cc: Li, WeiyuanX <weiyuanx.li@intel.com>
Subject: [dts][PATCH V1 1/2] tests/smoke_base modify ixgbe support vf jumbo verify.
the ixgbe NIC only supports one global MTU per physical port.
So when the user sets different MTUs on PF and VF ports in one physical port, the real MTU for all these PF and VF ports is the largest value set.
This behavior is based on the kernel driver behavior.
So, modify script supports the verification packet sent is greater than PF MTU for ixgbe driver.
Signed-off-by: Weiyuan Li <weiyuanx.li@intel.com>
prev parent reply other threads:[~2022-05-10 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 7:46 Weiyuan Li
2022-05-09 7:46 ` [dts][PATCH V1 2/2] tests/vf_smoke " Weiyuan Li
2022-05-10 2:46 ` Chen, LingliX
2022-05-10 3:31 ` Peng, Yuan [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=CO1PR11MB50580433C7EDD1D7B1F60E9DFEC99@CO1PR11MB5058.namprd11.prod.outlook.com \
--to=yuan.peng@intel.com \
--cc=dts@dpdk.org \
--cc=weiyuanx.li@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).