From: David Marchand <david.marchand@redhat.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Li Han <han.li1@zte.com.cn>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v5 1/2] eal: make base address hint OS-specific
Date: Sat, 26 Oct 2019 18:02:35 +0200 [thread overview]
Message-ID: <CAJFAV8wcifRDHPH2KtbJtASoz_M4iv2gvMMhdETEoKp95cwJHw@mail.gmail.com> (raw)
In-Reply-To: <ea8457f47a25f20f59bb1f37dcf2a1f0bf340c9d.1571920604.git.anatoly.burakov@intel.com>
On Thu, Oct 24, 2019 at 2:37 PM Anatoly Burakov
<anatoly.burakov@intel.com> wrote:
>
> Not all OS's follow Linux's memory layout, which may lead to
> problems following the suggested common address hint absent
> of a base-virtaddr flag. Make this address hint OS-specific.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks.
--
David Marchand
next prev parent reply other threads:[~2019-10-26 16:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 12:42 [dpdk-dev] [PATCH " 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
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 ` David Marchand [this message]
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=CAJFAV8wcifRDHPH2KtbJtASoz_M4iv2gvMMhdETEoKp95cwJHw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=han.li1@zte.com.cn \
--cc=stable@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 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).