From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4 1/2] eal: make base address hint OS-specific
Date: Thu, 24 Oct 2019 13:32:06 +0100 [thread overview]
Message-ID: <7e8c860a-cf9b-8be7-8b7e-5af27ea72b39@intel.com> (raw)
In-Reply-To: <CAJFAV8wmuoFOwcnH9OXupOCVX9-fXsRNNDeccefjZeUPDWH-Zw@mail.gmail.com>
On 02-Oct-19 12:41 PM, David Marchand wrote:
> On Wed, Jul 31, 2019 at 2:47 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
>
> Missing Fixes: ?
No, not really. This isn't a bug as such - it was intended behavior.
It's just /wrong/ intended behavior :)
>
> What about windows port?
>
>
I don't see it supporting secondary processes or mapping shared config
anywhere. So probably unimplemented for now.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-10-24 12:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 12:42 [dpdk-stable] [PATCH " Anatoly Burakov
2019-07-29 11:10 ` Anatoly Burakov
2019-07-29 11:18 ` Anatoly Burakov
2019-07-29 12:42 ` [dpdk-stable] [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 ` [dpdk-stable] [dpdk-dev] " Burakov, Anatoly
2019-07-30 15:37 ` [dpdk-stable] [PATCH v2 1/2] eal: make base address hint OS-specific Anatoly Burakov
2019-07-30 15:51 ` [dpdk-stable] [PATCH v3 " Anatoly Burakov
2019-07-31 12:47 ` [dpdk-stable] [PATCH v4 " Anatoly Burakov
2019-10-02 11:41 ` [dpdk-stable] [dpdk-dev] " David Marchand
2019-10-02 14:42 ` Stephen Hemminger
2019-10-24 12:32 ` Burakov, Anatoly
2019-10-24 12:32 ` Burakov, Anatoly [this message]
2019-10-24 12:36 ` [dpdk-stable] [PATCH v5 " Anatoly Burakov
2019-10-26 16:02 ` David Marchand
2019-10-24 12:36 ` [dpdk-stable] [PATCH v5 2/2] eal: use base address hint to reserve space for mem config Anatoly Burakov
2019-10-26 16:02 ` David Marchand
2019-07-31 12:47 ` [dpdk-stable] [PATCH v4 " Anatoly Burakov
2019-07-30 15:51 ` [dpdk-stable] [PATCH v3 " Anatoly Burakov
2019-07-30 15:37 ` [dpdk-stable] [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=7e8c860a-cf9b-8be7-8b7e-5af27ea72b39@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.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).