From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Removing more mbuf fields
Date: Thu, 05 Nov 2020 08:20:15 +0100 [thread overview]
Message-ID: <5534102.fTr2JavNfC@thomas> (raw)
In-Reply-To: <20201104154243.4fd3a03c@hermes.local>
05/11/2020 00:42, Stephen Hemminger:
> Thanks for the work cleaning out some of the cruft in the mbuf to make space
> for dynamic fields.
>
> Are you going to breakup the hash union in mbuf?
> There is some bits to be gained there for dynamic fields.
>
> - Flow director should be deprecated/gone/killed so hash.fdir can disappear.
>
> - QoS scheduling hash.sched should be a dynamic field.
>
> - Eventdev hash.tx_adapter.txq should be a dynamic field as well.
>
> - hash.usr field is obviously an dynamic field candidate.
>
> That leaves only hash.rss which is smaller (32 instead of 64 bits in union)
> and should stay.
Yes such dynamic fields can be used during next year,
so we are prepared to remove more fields in 21.11 next year.
I hope such cleanup can be contributing by multiple volunteers.
prev parent reply other threads:[~2020-11-05 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 23:42 [dpdk-dev] Removing more mbuf fields Stephen Hemminger
2020-11-05 7:20 ` Thomas Monjalon [this message]
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=5534102.fTr2JavNfC@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.