From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: announce@dpdk.org
Subject: [dpdk-announce] Memory Hotplug patchset for DPDK
Date: Fri, 16 Mar 2018 14:31:34 +0000 [thread overview]
Message-ID: <b2ad3676-923e-7d45-ea8e-5bd82db806d8@intel.com> (raw)
Hi all,
I would like to draw your attention to Memory Hotplug patchset that is
targeted for 18.05.
Because of the amount of code and potential implications of such a major
EAL memory plumbing rework involved, I would like to ask everyone
interested in this work (particularly representatives of the companies
on DPDK tech board – NXP, Cavium, etc.) to review and test this patchset
in the shortest timeframe possible.
In order to ease the pain of testing, a GitHub repository was created:
https://github.com/anatolyburakov/dpdk
The patches up on the mailing list require a few prerequisite patches to
be applied and are currently out of date from the GitHub repo, so using
GitHub repository is the (highly) preferred method of testing. (v3
rework with all GitHub changes integrated is in progress)
It would be good to merge this some time before the integration
deadline, as there are a lot of other patchsets that may potentially be
affected by the merge.
--
Thanks,
Anatoly
reply other threads:[~2018-03-16 14:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b2ad3676-923e-7d45-ea8e-5bd82db806d8@intel.com \
--to=anatoly.burakov@intel.com \
--cc=announce@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).