From: hch@infradead.org (Christoph Hellwig)
Subject: guaranteed progress for NVME commands?
Date: Tue, 22 Mar 2016 00:45:31 -0700 [thread overview]
Message-ID: <20160322074531.GA32289@infradead.org> (raw)
Hi All,
in SCSI and other block drivers we go through great pains to only
use mempool backed allocations in the I/O path, so that we can make
guaranteed progress for swap or the writeback daemons. But it seems
like the NVMe driver is using plain kmalloc everywhere and seems to
be getting away with that just for now. Is no one using swap on
NVMe or am I missing a secret trick somewhere?
next reply other threads:[~2016-03-22 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 7:45 Christoph Hellwig [this message]
2016-03-22 14:46 ` guaranteed progress for NVME commands? Keith Busch
2016-03-22 17:57 ` Keith Busch
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=20160322074531.GA32289@infradead.org \
--to=hch@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