From: Daniel Kirichok <dkirichok@iol.unh.edu>
To: dts@dpdk.org
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
David Liu <dliu@iol.unh.edu>,
Owen Hilyard <ohilyard@iol.unh.edu>
Subject: [dts] LRO Feature Question
Date: Wed, 8 Jul 2020 12:21:30 -0400 [thread overview]
Message-ID: <CAFRcHM3a-18PRZRWA8WUJ=_xB5rB8KKQzSagHp=Nq60GDVM0sw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hi all,
For developing the LRO test case, the related functionality that it looks
like testpmd has is to configure per port Rx offloading to be tcp_lro and
to set the maximum LRO aggregated packet size. Would only these two
configurations be enough to thoroughly test the LRO functionality?
Thanks,
Dan
--
Dan Kirichok
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
dkirichok@iol.unh.edu
www.iol.unh.edu
[-- Attachment #2: Type: text/html, Size: 2437 bytes --]
reply other threads:[~2020-07-08 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAFRcHM3a-18PRZRWA8WUJ=_xB5rB8KKQzSagHp=Nq60GDVM0sw@mail.gmail.com' \
--to=dkirichok@iol.unh.edu \
--cc=dliu@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=lylavoie@iol.unh.edu \
--cc=ohilyard@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).