From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
adilger@dilger.ca, martin.petersen@oracle.com
Subject: Re: [PATCH 04/11] fs: add support for allowing applications to pass in write life time hints
Date: Tue, 20 Jun 2017 05:43:55 -0700 [thread overview]
Message-ID: <20170620124355.GA6199@infradead.org> (raw)
In-Reply-To: <6f1be22c-b172-3645-f0ab-8124188756df@kernel.dk>
On Tue, Jun 20, 2017 at 06:43:10AM -0600, Jens Axboe wrote:
> > Question: IFF we can get the per-file hints to propagate to the
> > writeback code (which I think is pretty easy for ext4/xfs/bdev, not
> > sure about btrfs) do we even need the per-inode ones at all?
>
> How is that possible, the file could be long gone by the time
> the writeback kicks in?
each time a page/buffer is dirtied we can propagate the hint.
next prev parent reply other threads:[~2017-06-20 12:43 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 19:59 [PATCHSET v7] Add support for write life time hints Jens Axboe
2017-06-17 19:59 ` [PATCH 01/11] fs: add support for an inode to carry write hint related data Jens Axboe
2017-06-19 6:26 ` Christoph Hellwig
2017-06-19 14:55 ` Jens Axboe
2017-06-17 19:59 ` [PATCH 02/11] block: add support for write hints in a bio Jens Axboe
2017-06-17 19:59 ` [PATCH 03/11] blk-mq: expose stream write hints through debugfs Jens Axboe
2017-06-17 19:59 ` [PATCH 04/11] fs: add support for allowing applications to pass in write life time hints Jens Axboe
2017-06-19 6:27 ` Christoph Hellwig
2017-06-19 14:56 ` Jens Axboe
2017-06-19 16:02 ` Jens Axboe
2017-06-19 18:58 ` Christoph Hellwig
2017-06-19 19:00 ` Jens Axboe
2017-06-19 19:10 ` Jens Axboe
2017-06-19 20:33 ` Jens Axboe
2017-06-20 2:06 ` Jens Axboe
2017-06-20 8:57 ` Christoph Hellwig
2017-06-20 12:43 ` Jens Axboe
2017-06-20 12:43 ` Christoph Hellwig [this message]
2017-06-20 12:45 ` Jens Axboe
2017-06-20 12:47 ` Christoph Hellwig
2017-06-20 12:51 ` Jens Axboe
2017-06-20 12:56 ` Christoph Hellwig
2017-06-20 13:00 ` Jens Axboe
2017-06-17 19:59 ` [PATCH 05/11] fs: add fcntl() interface for setting/getting " Jens Axboe
2017-06-19 6:28 ` Christoph Hellwig
2017-06-19 14:57 ` Jens Axboe
2017-06-17 19:59 ` [PATCH 06/11] fs: add O_DIRECT support for sending down " Jens Axboe
2017-06-19 6:28 ` Christoph Hellwig
2017-06-19 14:57 ` Jens Axboe
2017-06-17 19:59 ` [PATCH 07/11] fs: add support for buffered writeback to pass down write hints Jens Axboe
2017-06-17 19:59 ` [PATCH 08/11] ext4: add support for passing in write hints for buffered writes Jens Axboe
2017-06-17 19:59 ` [PATCH 09/11] xfs: " Jens Axboe
2017-06-17 19:59 ` [PATCH 10/11] btrfs: " Jens Axboe
2017-06-17 19:59 ` [PATCH 11/11] nvme: add support for streams and directives Jens Axboe
2017-06-19 6:35 ` Christoph Hellwig
2017-06-19 15:04 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2017-06-16 17:24 [PATCHSET v6] Add support for write life time hints Jens Axboe
2017-06-16 17:24 ` [PATCH 04/11] fs: add support for allowing applications to pass in " Jens Axboe
2017-06-15 3:45 [PATCHSET v4] Add support for " Jens Axboe
2017-06-15 3:45 ` [PATCH 04/11] fs: add support for allowing applications to pass in " Jens Axboe
2017-06-15 4:15 ` Darrick J. Wong
2017-06-15 4:33 ` Jens Axboe
2017-06-15 8:19 ` Christoph Hellwig
2017-06-15 14:21 ` Jens Axboe
2017-06-15 15:23 ` Jens Axboe
2017-06-16 7:30 ` Christoph Hellwig
2017-06-16 14:35 ` Jens Axboe
2017-06-16 7:33 ` Christoph Hellwig
2017-06-16 14:35 ` Jens Axboe
2017-06-16 14:53 ` Jens Axboe
2017-06-16 15:52 ` Christoph Hellwig
2017-06-16 15:59 ` Jens Axboe
2017-06-16 16:14 ` Jens Axboe
2017-06-16 18:00 ` Christoph Hellwig
2017-06-16 18:02 ` Christoph Hellwig
2017-06-16 19:35 ` Jens Axboe
2017-06-15 11:24 ` Al Viro
2017-06-14 19:05 [PATCHSET v3] Add support for " Jens Axboe
2017-06-14 19:05 ` [PATCH 04/11] fs: add support for allowing applications to pass in " Jens Axboe
2017-06-14 20:26 ` Christoph Hellwig
2017-06-14 20:37 ` Jens Axboe
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=20170620124355.GA6199@infradead.org \
--to=hch@infradead.org \
--cc=adilger@dilger.ca \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).