From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1432] net/tap: use kernel for TSO offload
Date: Thu, 02 May 2024 02:33:19 +0000 [thread overview]
Message-ID: <bug-1432-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1432
Bug ID: 1432
Summary: net/tap: use kernel for TSO offload
Product: DPDK
Version: 24.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
The kernel TAP device supports TSO for doing segmentation offload.
This should be used instead of doing GSO inside the TAP PMD because it will
improve performance.
If using kernel TSO, no copy is necessary in PMD and only a single syscall
would be needed for the TSO mbuf. For example, sending a 64K TSO mbuf would
become single writev(); instead of multiple allocations and copies followed by
multiple writev's.
Doing this would also simplfy code and error handling.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2885 bytes --]
reply other threads:[~2024-05-02 2:33 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=bug-1432-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).