DPDK patches and discussions
 help / color / Atom feed
From: "Zhou, JunX W" <junx.w.zhou@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] eal/mem: preallocate VA	space in no-huge mode
Date: Fri, 27 Mar 2020 02:23:46 +0000
Message-ID: <EDA4914C4BAB5848BD29F696B5FE612D043E2E49@CDSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <6473a4fe45d8437285fd8a1e931a1cb8@intel.com>

Tested-by: Zhou, JunX W <junx.w.zhou@intel.com>
-----Original Message-----
From: Jiang, YuX 
Sent: Thursday, March 26, 2020 8:24 PM
To: David Marchand <david.marchand@redhat.com>; Burakov, Anatoly <anatoly.burakov@intel.com>
Cc: dev <dev@dpdk.org>; dpdk stable <stable@dpdk.org>; Zhou, JunX W <junx.w.zhou@intel.com>
Subject: RE: [dpdk-dev] [dpdk-stable] [PATCH v3] eal/mem: preallocate VA space in no-huge mode

+  Zhou, JunX W <junx.w.zhou@intel.com>

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of David Marchand
Sent: Wednesday, March 25, 2020 10:40 PM
To: Burakov, Anatoly <anatoly.burakov@intel.com>
Cc: dev <dev@dpdk.org>; dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] eal/mem: preallocate VA space in no-huge mode

On Fri, Feb 7, 2020 at 12:11 PM Anatoly Burakov <anatoly.burakov@intel.com> wrote:
> When --no-huge mode is used, the memory is currently allocated with 
> mmap(NULL, ...). This is fine in most cases, but can fail in cases 
> where DPDK is run on a machine with an IOMMU that is of more limited 
> address width than that of a VA, because we're not specifying the 
> address hint for mmap() call.
> Fix it by preallocating VA space before mapping it.
> Cc: stable@dpdk.org
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>

Reproduced issue reported by Thomas on v2.
Works fine with v3.

Tested-by: David Marchand <david.marchand@redhat.com>

Does this issue affect FreeBSD too?

David Marchand

  parent reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 17:01 [dpdk-dev] [PATCH] " Anatoly Burakov
2020-01-24 17:05 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov
2020-02-06 15:39   ` Thomas Monjalon
2020-02-06 21:07     ` Thomas Monjalon
2020-02-07 11:11   ` [dpdk-dev] [PATCH v3] " Anatoly Burakov
2020-03-25 14:39     ` [dpdk-dev] [dpdk-stable] " David Marchand
2020-03-26 17:06       ` Burakov, Anatoly
2020-03-27  6:33         ` David Marchand
     [not found]       ` <6473a4fe45d8437285fd8a1e931a1cb8@intel.com>
2020-03-27  2:23         ` Zhou, JunX W [this message]
2020-03-27 10:16       ` David Marchand

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EDA4914C4BAB5848BD29F696B5FE612D043E2E49@CDSMSX102.ccr.corp.intel.com \
    --to=junx.w.zhou@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
	public-inbox-index dev

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox