From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org
Subject: [PATCH v3 0/2] app/testpmd: support TCP TSO in Tx only mode
Date: Fri, 11 Nov 2022 12:04:21 +0300 [thread overview]
Message-ID: <20221111090423.1600091-1-andrew.rybchenko@oktetlabs.ru> (raw)
In-Reply-To: <20221017144133.1899052-1-andrew.rybchenko@oktetlabs.ru>
Add command-line option to generate TSO packets with specified MSS
in txonly mode.
I'm not sure that it is a good idea to enable TSO offload automaticaly
when the options is specified, but it is convenient.
v3:
- a bit better fix of review notes from Ferruh
v2:
- fix wrong data length calculation (as per review notes from Ferruh)
Andrew Rybchenko (2):
app/testpmd: prepare to support TCP in Tx only mode
app/testpmd: support TCP TSO in Tx only mode
app/test-pmd/parameters.c | 16 ++-
app/test-pmd/testpmd.c | 12 +++
app/test-pmd/testpmd.h | 5 +-
app/test-pmd/txonly.c | 141 +++++++++++++++++++-------
doc/guides/testpmd_app_ug/run_app.rst | 4 +
5 files changed, 135 insertions(+), 43 deletions(-)
--
2.30.2
next prev parent reply other threads:[~2022-11-11 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 14:41 [PATCH " Andrew Rybchenko
2022-10-17 14:41 ` [PATCH 1/2] app/testpmd: prepare to support TCP " Andrew Rybchenko
2022-10-19 16:39 ` Ferruh Yigit
2022-11-11 8:36 ` Andrew Rybchenko
2022-11-11 8:54 ` Andrew Rybchenko
2022-11-15 12:32 ` Ferruh Yigit
2022-10-17 14:41 ` [PATCH 2/2] app/testpmd: support TCP TSO " Andrew Rybchenko
2022-10-19 16:41 ` Ferruh Yigit
2022-11-11 8:44 ` Andrew Rybchenko
2022-11-11 9:04 ` Andrew Rybchenko [this message]
2022-11-11 9:04 ` [PATCH v3 1/2] app/testpmd: prepare to support TCP " Andrew Rybchenko
2022-11-11 9:04 ` [PATCH v3 2/2] app/testpmd: support TCP TSO " Andrew Rybchenko
2022-11-15 12:43 ` Ferruh Yigit
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=20221111090423.1600091-1-andrew.rybchenko@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.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).