From: Michael Moy <michael@moysys.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] fs: pass the write life time hint to the mapped filesystem
Date: Mon, 18 Sep 2017 14:06:27 -0600 [thread overview]
Message-ID: <661c0a72-43c5-53bf-8f8d-4f95283ddc8d@moysys.com> (raw)
In-Reply-To: <20170918154939.GA13431@lst.de>
Thanks, I see that now.
What is the file hint using F_SET_FILE_RW_HINT used for?
It seems that if both are set, the one set first gets used
and, if only the file hint is set, it is not used at all.
On 9/18/2017 9:49 AM, Christoph Hellwig wrote:
> 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.
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>
prev parent reply other threads:[~2017-09-18 20:06 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
2017-09-18 20:06 ` Michael Moy [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=661c0a72-43c5-53bf-8f8d-4f95283ddc8d@moysys.com \
--to=michael@moysys.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.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