From: Andrew Bailey <abailey@iol.unh.edu>
To: luca.vizzarro@arm.com
Cc: dev@dpdk.org, dmarx@iol.unh.edu, probb@iol.unh.edu
Subject: Re: [PATCH v1 0/3] dts: add tx_offload support in dts
Date: Tue, 2 Sep 2025 07:48:45 -0400 [thread overview]
Message-ID: <CABJ3N2UbixNX3Rejm1Ch+KaVqtedxw7xsUm4W5uYfM_zhAQtYA@mail.gmail.com> (raw)
In-Reply-To: <20250902114327.48185-1-abailey@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
This patch set in its entirety was sent by mistake, please ignore.
On Tue, Sep 2, 2025 at 7:43 AM Andrew Bailey <abailey@iol.unh.edu> wrote:
> This patchset introduces the support for TX offload configuration
> through DTS, allowing test cases to be written utilizing TX offload
> capabilities. Along with configuring these capabilities, they are also
> added to the NIC capabilities class, in which they can be required by
> test suites. Finally, a test suite was created using the aforementioned
> changes to update the RX TX offload test suite in legacy DTS.
>
> Andrew Bailey (3):
> dts: add TX offload capabilities to NIC capabilities
> dts: allow mbuf_fast_free to be set with testpmd shell
> dts: update tx_offload test from old dts
>
> dts/framework/remote_session/testpmd_shell.py | 340 +++++++++++++++++-
> dts/tests/TestSuite_rxtx_offload.py | 153 ++++++++
> 2 files changed, 492 insertions(+), 1 deletion(-)
> create mode 100644 dts/tests/TestSuite_rxtx_offload.py
>
> --
> 2.50.1
>
>
[-- Attachment #2: Type: text/html, Size: 1397 bytes --]
next prev parent reply other threads:[~2025-09-02 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 11:43 Andrew Bailey
2025-09-02 11:43 ` [PATCH v1 1/3] dts: fix docstring typo in checksum suite Andrew Bailey
2025-09-02 11:43 ` [PATCH v1 2/3] dts: add reception check to checksum offload suite Andrew Bailey
2025-09-02 11:43 ` [PATCH v1 3/3] dts: all are one Andrew Bailey
2025-09-02 11:48 ` Andrew Bailey [this message]
2025-09-02 14:27 [PATCH v1 0/3] dts: add tx_offload support in dts Andrew Bailey
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=CABJ3N2UbixNX3Rejm1Ch+KaVqtedxw7xsUm4W5uYfM_zhAQtYA@mail.gmail.com \
--to=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=luca.vizzarro@arm.com \
--cc=probb@iol.unh.edu \
/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).