From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>, linux-nvme@lists.infradead.org
Subject: Re: [RFC] nvme-cli: Support for hugetlbfs
Date: Tue, 5 Nov 2019 17:20:03 -0700 [thread overview]
Message-ID: <27eb0ed1-a31a-c466-7158-73d8fb5349d3@kernel.dk> (raw)
In-Reply-To: <20191105183412.333-1-kbusch@kernel.org>
On 11/5/19 11:34 AM, Keith Busch wrote:
> Some commands require exceptionally large data transfers, and the
> kernel driver supports only a limited number of phyiscal segments per
> command. To help support large transfers, try to allocate physically
> contiguous space via hugetlbfs.
>
> Rather than deal with the nuances of allocating huge pages, this patch
> requires libhugetlbfs be installed on the host system.
LGTM, and solves a real issue with user issued admin commands that we
can't break up.
Reviewed-by: Jens Axboe <axboe@kernel.dk>
--
Jens Axboe
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-11-06 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 18:34 [RFC] nvme-cli: Support for hugetlbfs Keith Busch
2019-11-05 20:35 ` Chaitanya Kulkarni
2019-11-06 0:49 ` Keith Busch
2019-11-06 0:20 ` Jens Axboe [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=27eb0ed1-a31a-c466-7158-73d8fb5349d3@kernel.dk \
--to=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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