From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] eal: use base address hint to reserve space for mem config
Date: Mon, 29 Jul 2019 14:13:18 +0100 [thread overview]
Message-ID: <45c91a5f-0e80-d60f-a789-bd9cf299a641@intel.com> (raw)
In-Reply-To: <3f4bf9cdf8b472e05e76274f6e8df5be936b01a9.1564398617.git.anatoly.burakov@intel.com>
On 29-Jul-19 12:18 PM, Anatoly Burakov wrote:
> Currently, mem config will be mapped without using the virtual
> area reservation infrastructure, which means it will be mapped
> at an arbitrary location. This may cause failures to map the
> shared config in secondary process due to things like PCI
> whitelist arguments allocating memory in a space where the
> primary has allocated the shared mem config.
>
> Fix this by using virtual area reservation to reserve space for
> the mem config, thereby avoiding the problem and reserving the
> shared config (hopefully) far away from any normal memory
> allocations.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
Apologies for multiple sends, the email appeared to not be getting
through...
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-07-29 13:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 12:42 [dpdk-dev] [PATCH 1/2] eal: make base address hint OS-specific Anatoly Burakov
2019-07-29 11:10 ` Anatoly Burakov
2019-07-29 11:18 ` Anatoly Burakov
2019-07-29 12:42 ` [dpdk-dev] [PATCH 2/2] eal: use base address hint to reserve space for mem config Anatoly Burakov
2019-07-29 11:10 ` Anatoly Burakov
2019-07-29 11:18 ` Anatoly Burakov
2019-07-29 13:13 ` Burakov, Anatoly [this message]
2019-07-30 15:37 ` [dpdk-dev] [PATCH v2 1/2] eal: make base address hint OS-specific Anatoly Burakov
2019-07-30 15:51 ` [dpdk-dev] [PATCH v3 " Anatoly Burakov
2019-07-31 12:47 ` [dpdk-dev] [PATCH v4 " Anatoly Burakov
2019-10-02 11:41 ` David Marchand
2019-10-02 14:42 ` Stephen Hemminger
2019-10-24 12:32 ` Burakov, Anatoly
2019-10-24 12:32 ` Burakov, Anatoly
2019-10-24 12:36 ` [dpdk-dev] [PATCH v5 " Anatoly Burakov
2019-10-26 16:02 ` [dpdk-dev] [dpdk-stable] " David Marchand
2019-10-24 12:36 ` [dpdk-dev] [PATCH v5 2/2] eal: use base address hint to reserve space for mem config Anatoly Burakov
2019-10-26 16:02 ` [dpdk-dev] [dpdk-stable] " David Marchand
2019-07-31 12:47 ` [dpdk-dev] [PATCH v4 " Anatoly Burakov
2019-07-30 15:51 ` [dpdk-dev] [PATCH v3 " Anatoly Burakov
2019-07-30 15:37 ` [dpdk-dev] [PATCH v2 " Anatoly Burakov
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=45c91a5f-0e80-d60f-a789-bd9cf299a641@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@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).