From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Iain Barker <iain.barker@oracle.com>,
"Wiles, Keith" <keith.wiles@intel.com>
Cc: dev@dpdk.org, Edwin Leung <edwin.leung@oracle.com>
Subject: Re: [dpdk-dev] Question about DPDK hugepage fd change
Date: Thu, 7 Feb 2019 11:15:31 +0000 [thread overview]
Message-ID: <e2080918-3205-953d-fdcd-cab402a13bcc@intel.com> (raw)
In-Reply-To: <aa530fd1-1292-4305-8ad3-093748725202@default>
On 06-Feb-19 1:57 PM, Iain Barker wrote:
>> Can you use 1G hugepages instead of 2M pages or a combo of the two, not sure how dpdk handles having both in the system?
>
> Unfortunately, no. Some of our customer deployments are tenancies on KVM hosts and low-end appliances, which are not configurable by the end user to enable 1G huge pages.
>
> I think we are going to have to revert this patch set from our build, as I don't see any other alternative for using DPDK 18 whilst remaining compliant to the POSIX/glibc requirements.
>
Yep, apologies for that. I think a new command-line flag to disable this
functionality should solve the issue, but we already have enough of those...
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-02-07 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 18:56 Iain Barker
2019-02-05 20:29 ` Wiles, Keith
2019-02-05 21:27 ` Iain Barker
2019-02-05 21:36 ` Wiles, Keith
2019-02-05 21:49 ` Iain Barker
2019-02-05 22:02 ` Wiles, Keith
2019-02-06 13:57 ` Iain Barker
2019-02-07 11:15 ` Burakov, Anatoly [this message]
2019-02-22 17:08 ` Burakov, Anatoly
2019-02-27 13:57 ` Iain Barker
2019-02-27 18:02 ` Edwin Leung
2019-02-28 10:36 ` Burakov, Anatoly
[not found] <1820650896.208393.1633616003335.ref@mail.yahoo.com>
2021-10-07 14:13 ` Vijay Atreya
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=e2080918-3205-953d-fdcd-cab402a13bcc@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=edwin.leung@oracle.com \
--cc=iain.barker@oracle.com \
--cc=keith.wiles@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 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).