From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: [dpdk-dev] Removing more mbuf fields
Date: Wed, 4 Nov 2020 15:42:43 -0800 [thread overview]
Message-ID: <20201104154243.4fd3a03c@hermes.local> (raw)
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.
next reply other threads:[~2020-11-04 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 23:42 Stephen Hemminger [this message]
2020-11-05 7:20 ` 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=20201104154243.4fd3a03c@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).