From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
axboe@fb.com, sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: remove support or stream based temperature hint
Date: Thu, 3 Mar 2022 18:57:08 +0100 [thread overview]
Message-ID: <20220303175708.GA21793@lst.de> (raw)
In-Reply-To: <c7be737d-9cf1-83b7-94f8-f4f0e3786eac@kernel.dk>
On Thu, Mar 03, 2022 at 07:50:05AM -0700, Jens Axboe wrote:
> > And without nvme, there doesn't appear to be a real user for the
> > write_hint anymore. All you can really do with it now is prevent
> > merging, which doesn't seem useful.
> >
>
> Yes, I would suggest that we just prune the write hint and just leave
> the fcntl() ops as stubs as a followup patch.
So we need to keep i_write_hint anyway for f2fs, but the block layer
removal is easy. It has some conflicts with other work, what tree
would you like it against?
prev parent reply other threads:[~2022-03-03 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 10:50 [PATCH] nvme: remove support or stream based temperature hint Christoph Hellwig
2022-03-03 13:30 ` Jens Axboe
2022-03-03 14:42 ` Keith Busch
2022-03-03 14:50 ` Jens Axboe
2022-03-03 17:57 ` 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=20220303175708.GA21793@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.