From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet: allow file backed ns to use cache
Date: Thu, 24 May 2018 10:04:15 +0200 [thread overview]
Message-ID: <20180524080415.GB11149@lst.de> (raw)
In-Reply-To: <20180523220016.6500-1-chaitanya.kulkarni@wdc.com>
I think this is mixing up two different issues - not using O_DIRECT
vs using O_SYNC. The first seems to useful to deal with things
like VDI setup, the latter doesn't really seem useful at all.
Note that for buffered I/O the kernel doesn't support asynch I/O,
so we really want to offload to a workqueue, except for posisbly
trying a RWF_NOWAIT attempt for reads first.
prev parent reply other threads:[~2018-05-24 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 22:00 [PATCH] nvmet: allow file backed ns to use cache Chaitanya Kulkarni
2018-05-24 8:04 ` Christoph Hellwig [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=20180524080415.GB11149@lst.de \
--to=hch@lst.de \
/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).