From: Meni Hillel <meni@shieldx.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] DPDK without Hugepages
Date: Thu, 8 Oct 2020 20:11:23 +0000 [thread overview]
Message-ID: <BYAPR20MB2888249BDA5F0F240AA0A2E0DD0B0@BYAPR20MB2888.namprd20.prod.outlook.com> (raw)
I am new to DPDK... I'd like to know if it is possible to use DPDK without the acceleration of hugepages, specifically rings, mbuf and hashmap, but not using accelerated networking.
I realize it will not be as performant, but is it possible? In case someone would want to know why would I want to do that is - we have already developed code that uses DPDK, were we control the OS, kernel, packaging etc. There is a portion of that we'd like to use in environment where we do not and cannot control kernel/os and thus would not be able to configure hugepages. For obvious reasons, we don't want to rewrite the code and use a different libraries.
I've noticed the docs has an option for no-huge but it is also claimed unsupported. So before we resort to desperate measures, I'm hoping it is possible.
Appreciate any help/advise.
Meni
reply other threads:[~2020-10-11 20:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BYAPR20MB2888249BDA5F0F240AA0A2E0DD0B0@BYAPR20MB2888.namprd20.prod.outlook.com \
--to=meni@shieldx.com \
--cc=users@dpdk.org \
/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).