From: Nicholas Pratte <npratte@iol.unh.edu>
To: paul.szczepanek@arm.com, jspewock@iol.unh.edu,
luca.vizzarro@arm.com, thomas@monjalon.net,
juraj.linkes@pantheon.tech, bruce.richardson@intel.com,
Honnappa.Nagarahalli@arm.com, probb@iol.unh.edu,
yoan.picchi@foss.arm.com
Cc: dev@dpdk.org
Subject: Re: [RFC PATCH 0/1] Initial Implementation For Jumbo Frames
Date: Fri, 24 May 2024 14:13:00 -0400 [thread overview]
Message-ID: <CAKXZ7eg4D_AzJ=doQqnAAxo10=a_qoGyhuxwBn=Ydt+MY6J7jQ@mail.gmail.com> (raw)
In-Reply-To: <20240524180616.18210-1-npratte@iol.unh.edu>
This is being superseded, ignore this submission.
Thanks.
On Fri, May 24, 2024 at 2:07 PM Nicholas Pratte <npratte@iol.unh.edu> wrote:
>
> The following is a rough design for the implementation of the jumbo
> frames test suite in new DTS. The test suite uses the same
> testing methodology from the test suite implementation in old
> DTS. In doing so, much of the logic in this implementation has been
> stripped away for the sake of maintaining an OS-agnostic design
> philosopgy. Thus, there are some concerns here that need further
> discussion.
>
> All test cases behave accordingly on lab hardware. However, issues with
> the testpmd shell, all of which will be fixed with the upcoming context
> manager, prevent the test suite from functioning properly if all test
> cases are run sequentially. Thus, for testing, each test case needs to
> be run individually. So, expect issues if attempting to test.
>
> Old DTS implements some basic logic that detects 1GB NICs, specifically
> when testing jumbo frame packets greater than the specified MTU length.
> This is because, according to a commit message from 2016, 1GB NICs will
> automatically adjust their size to +4 bytes, meaning that when setting
> an MTU of 9000, testpmd adjust the MTU size to 9004. To compensate, some
> logic was inserted in the old suite to adjust packet sizes accordingly.
> Given that Juraj's capabilities patch is in development, it would be
> possible to set a restriction on this test suite to remove the support
> of 1GB NICs, which could be determined from testpmd outputs; it could
> also be possible that this problem is entirely null and void today,
> essentially allowing us to forget about it.
>
> The current implementation is not developed with both the capabilities
> patch and the params patch in mind; however, the current design can and
> will be refactored to do so.
>
> Nicholas Pratte (1):
> Initial Implementation For Jumbo Frames Test Suite
>
> dts/framework/config/conf_yaml_schema.json | 3 +-
> dts/framework/test_suite.py | 8 +
> dts/tests/TestSuite_jumboframes.py | 210 +++++++++++++++++++++
> 3 files changed, 220 insertions(+), 1 deletion(-)
> create mode 100644 dts/tests/TestSuite_jumboframes.py
>
> --
> 2.44.0
>
next prev parent reply other threads:[~2024-05-24 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 18:06 Nicholas Pratte
2024-05-24 18:06 ` [RFC PATCH 1/1] Initial Implementation For Jumbo Frames Test Suite Nicholas Pratte
2024-05-24 18:13 ` Nicholas Pratte [this message]
2024-05-24 18:36 [RFC PATCH 0/1] Initial Implementation For Jumbo Frames Nicholas Pratte
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='CAKXZ7eg4D_AzJ=doQqnAAxo10=a_qoGyhuxwBn=Ydt+MY6J7jQ@mail.gmail.com' \
--to=npratte@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=yoan.picchi@foss.arm.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).