From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: <dev@dpdk.org>, <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [RFC] mbuf: performance optimization
Date: Sun, 21 Jan 2024 09:07:32 -0800 [thread overview]
Message-ID: <20240121090732.3cf8c5d6@hermes.local> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F17D@smartserver.smartshare.dk>
On Sun, 21 Jan 2024 06:32:42 +0100
Morten Brørup <mb@smartsharesystems.com> wrote:
> I suppose that reducing mbuf->nb_segs from 16 to 8 bit is realistic, considering that a maximum size IP packet (64 KB) is unlikely to use more than 64 plus some segments. Does anyone know of any use case with more than 255 segments in an mbuf?
There is the case of Linux internally using super large IPv6 (and now IPv4) frames.
See RFC 2675 IPv6 jumbograms
https://netdevconf.info/0x15/slides/35/BIG%20TCP.pdf
next prev parent reply other threads:[~2024-01-21 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 5:32 Morten Brørup
2024-01-21 17:07 ` Stephen Hemminger [this message]
2024-01-21 17:19 ` Morten Brørup
2024-01-22 14:27 ` [PATCH v2] mempool: test performance with larger bursts Morten Brørup
2024-01-22 14:39 ` Morten Brørup
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=20240121090732.3cf8c5d6@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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).