From: Thomas Monjalon <thomas@monjalon.net>
To: Jonas Pfefferle <jpf@zurich.ibm.com>
Cc: dev@dpdk.org, anatoly.burakov@intel.com, chaozhu@linux.vnet.ibm.com
Subject: Re: [dpdk-dev] [PATCH] eal/ppc: revert fix mmap for memory initialization
Date: Tue, 07 Nov 2017 00:30:51 +0100 [thread overview]
Message-ID: <2195471.a96TPSDOjF@xps> (raw)
In-Reply-To: <1509631099-31832-1-git-send-email-jpf@zurich.ibm.com>
02/11/2017 14:58, Jonas Pfefferle:
> This reverts commit 284ae3e9ff9a92575c28c858efd2c85c8de6d440
> ("eal/ppc: fix mmap for memory initialization").The logic if the
> address hint is respected on mmap is no different on POWER than
> on x86 however the address layout of userspace applications might
> be slightly different i.e. you might need to use a different
> virt-baseaddr. We now warn if the address hint is not respected
> (fae209f) thus users can try different virtual address bases.
It depends on a patch which is not applied yet.
prev parent reply other threads:[~2017-11-06 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 13:58 Jonas Pfefferle
2017-11-06 23:30 ` Thomas Monjalon [this message]
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=2195471.a96TPSDOjF@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=jpf@zurich.ibm.com \
/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).