From: Christoph Hellwig <hch@lst.de>
To: Michael Moy <michael@moysys.com>
Cc: axboe@kernel.dk, hch@lst.de, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH v2] fs: pass the write life time hint to the mapped filesystem
Date: Mon, 18 Sep 2017 17:49:39 +0200 [thread overview]
Message-ID: <20170918154939.GA13431@lst.de> (raw)
In-Reply-To: <2f7829a5-d47b-e6a0-cc10-8b534e9772ab@moysys.com>
On Mon, Sep 18, 2017 at 09:45:57AM -0600, Michael Moy wrote:
> The write hint needs to be copied to the mapped filesystem
> so it can be passed down to the nvme device driver.
>
> v2: fix tabs in the email
If you want the write hint for buffered I/O you need to set it on the
inode using F_SET_RW_HINT.
With your patch we'd magically move the file hint to the inode hint
on each write.
next prev parent reply other threads:[~2017-09-18 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 15:45 [PATCH v2] fs: pass the write life time hint to the mapped filesystem Michael Moy
2017-09-18 15:49 ` Christoph Hellwig [this message]
2017-09-18 20:06 ` Michael Moy
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=20170918154939.GA13431@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=michael@moysys.com \
/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