From: "Wiles, Keith" <keith.wiles@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Kevin Wilson <wkevils@gmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Hugepage size on x86 architectures:
Date: Mon, 7 Aug 2017 13:21:30 +0000 [thread overview]
Message-ID: <0610CAE8-A7BD-476F-A70C-9BF33A09015D@intel.com> (raw)
In-Reply-To: <20170806135607.1de07783@xeon-e3>
> On Aug 6, 2017, at 3:56 PM, Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> On Sun, 6 Aug 2017 13:31:48 +0300
> Kevin Wilson <wkevils@gmail.com> wrote:
>
>> Is it possible to use in DPDK other hugepage size than 2MB and 1GB (in
>> order to benchmark performance)
>> on x86 architectures)?
At this point we only have 4K, 2M and 1G, 4K is the normal page size and not strictly a huge page :-)
The hardware needs to be able to support hugepages and the Linux kernel. Running without huge pages is one option you can select from the command line.
>
> I think this is a CPU hardware restriction.
Regards,
Keith
prev parent reply other threads:[~2017-08-07 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 10:31 Kevin Wilson
2017-08-06 20:56 ` Stephen Hemminger
2017-08-07 13:21 ` Wiles, Keith [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=0610CAE8-A7BD-476F-A70C-9BF33A09015D@intel.com \
--to=keith.wiles@intel.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=wkevils@gmail.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).