From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] EAL lcore config
Date: Tue, 2 Apr 2019 20:04:52 -0700 [thread overview]
Message-ID: <20190402200452.7dd4f029@shemminger-XPS-13-9360> (raw)
Currently the DPDK Environment Abstraction Layer has its guts on the floor ;-)
The data structure for lcore config is a holey mess and changing it would
break the ABI.
I propose that for 19.05 we introduce accessor functions and change all
internal (out side of eal directory) to use those. And add a deprecation notice.
For 19.08, we can mark the data structure as deprecated but keep it
the same. Any thing built from source that hits the global variable
will get a warning. Binaries will still run unmodified.
For 19.11, lcore_config can be moved to eal_private.h where it belongs,
and some simple rearrangements will shrink it and get almost all data
on the same cache line. This breaks ABI but API stays the same as 19.05
After that some of the debris can be cleaned out without affecting
API or ABI in future.
next reply other threads:[~2019-04-03 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 3:04 Stephen Hemminger [this message]
2019-04-03 3:04 ` Stephen Hemminger
2019-04-03 9:58 ` Burakov, Anatoly
2019-04-03 9:58 ` Burakov, Anatoly
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=20190402200452.7dd4f029@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.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 NNTP newsgroup(s).