> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Sunday, 21 January 2024 18.08
>
> On Sun, 21 Jan 2024 06:32:42 +0100
> Morten Brørup 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 unli
On Sun, 21 Jan 2024 06:32:42 +0100
Morten Brørup 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 segment
What is the largest realistic value of mbuf->priv_size (the size of an mbuf's
application private data area) in any use case?
I am wondering if its size could be reduced from 16 to 8 bit. If a max value of
255 isn't enough, then perhaps by knowing that the private data area must be
aligned by 8
I have been playing around with the idea to make some changes to avoid using
the mbuf's 2nd cache line in many common cases, which would reduce the cache
pressure significantly, and thus improve performance. I would like to discuss
if it is doable. (And let's just assume that ABI breakage is an
4 matches
Mail list logo
