From: E.W.Z. <kreuzerkrieg at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK without hugepages?
Date: Wed, 23 Jan 2019 18:14:28 +0200 [thread overview]
Message-ID: <5c4892e2.1c69fb81.7bfae.9204@mx.google.com> (raw)
In-Reply-To: CANvN+emwA9Rcq5WPpB2k7y01XdDQdq=YzBUC7tR89PO38zuLiw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
As far as I understand DPDK is capable of doing both.
Nothing wrong with hugepages except the fact that I have to enable hugepages on host machines where my application is going to run. This is additional requirement for the host machine I would like to avoid.
Sent from Mail for Windows 10
From: Andrey Kuzmin
Sent: Wednesday, January 23, 2019 17:05
To: Storage Performance Development Kit
Subject: Re: [SPDK] SPDK without hugepages?
On Wed, Jan 23, 2019 at 6:00 PM Ernest Zed <kreuzerkrieg(a)gmail.com> wrote:
> Looks like in the past there was an attempt to work without hugepages, as
> in `init.c` was a line of code like `args = spdk_push_arg(args, &argcount,
> _sprintf_alloc("--no-huge"));` Looks like it didnt work and was removed.
> So, is it possible?
For that to work, an alternative to huge pages is needed that, at the very
minimum, possesses the same basic qualities:
1) Never ever paged out,
2) Constant-time vtophys translation.
> Any plans to revive this feature? I'm interested in
> getting the NVMe Driver working without hugepages
>
And what's wrong with huge pages?
Regards,
Andrey
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
>
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2019-01-23 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 16:14 E.W.Z. [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-23 17:30 [SPDK] SPDK without hugepages? E.W.Z.
2019-01-23 17:15 Walker, Benjamin
2019-01-23 15:05 Andrey Kuzmin
2019-01-23 14:55 Ernest Zed
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=5c4892e2.1c69fb81.7bfae.9204@mx.google.com \
--to=spdk@lists.01.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