From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, sergio.gonzalez.monroy@intel.com,
david.marchand@6wind.com, pmatilai@redhat.com
Subject: Re: [PATCH v2] mem: revert page locking when not using hugepages
Date: Thu, 30 Jun 2016 19:17:12 +0200 [thread overview]
Message-ID: <2064760.ObAVrGWHUJ@xps13> (raw)
In-Reply-To: <1467043131-24658-1-git-send-email-olivier.matz@6wind.com>
2016-06-27 17:58, Olivier Matz:
> This reverts commit 593a084afc2b441895aeca78a2c4465e450d0ef5.
>
> Since recently [1], it is not possible to run the dpdk with
> non-root privileges and the --no-huge option. This is because the eal
> layer tries to lock the memory. Using locked memory is mandatory for
> physical devices because they reference physical addresses.
>
> But a user may want to start the dpdk without locked memory, because he
> does not have the permission to do so, and/or does not have this need,
> for instance because he uses virtual drivers.
>
> So this commit reverts the use of MAP_LOCKED in mmap() flags.
>
> [1] http://www.dpdk.org/ml/archives/dev/2016-May/039404.html
>
> Fixes: 593a084afc2b ("mem: lock pages when not using hugepages")
> Reported-by: Panu Matilainen <pmatilai@redhat.com>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
Applied, thanks
Let's keep in mind to make things working with --no-huge.
prev parent reply other threads:[~2016-06-30 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 10:26 [PATCH] mem: skip memory locking on failure Olivier Matz
2016-06-14 13:21 ` Panu Matilainen
2016-06-14 14:12 ` Olivier MATZ
2016-06-21 11:58 ` Panu Matilainen
2016-06-27 15:58 ` [PATCH v2] mem: revert page locking when not using hugepages Olivier Matz
2016-06-30 17:17 ` 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=2064760.ObAVrGWHUJ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=pmatilai@redhat.com \
--cc=sergio.gonzalez.monroy@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.