From: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com
Subject: [PATCH] doc: clarify ipsec-secgw documentation on TSO
Date: Wed, 27 Mar 2024 10:51:13 +0000 [thread overview]
Message-ID: <20240327105113.3116549-1-vladimir.medvedkin@intel.com> (raw)
Updated ipsec-secgw user guide to reflect that ipsec-secgw only
supports TSO for TCP/IP at this time.
Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
---
doc/guides/sample_app_ug/ipsec_secgw.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst
index 3686948833..cada8c375f 100644
--- a/doc/guides/sample_app_ug/ipsec_secgw.rst
+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst
@@ -765,6 +765,7 @@ where each options means:
``<mss>``
* Maximum segment size for TSO offload, available for egress SAs only.
+ Currently only supports TCP/IP.
* Optional: Yes, TSO offload not set by default
--
2.34.1
next reply other threads:[~2024-03-27 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 10:51 Vladimir Medvedkin [this message]
2024-03-27 11:10 ` Mcnamara, John
2024-03-27 22:29 ` Thomas Monjalon
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=20240327105113.3116549-1-vladimir.medvedkin@intel.com \
--to=vladimir.medvedkin@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).