From: "Luca Porzio (lporzio)" <lporzio@micron.com>
To: Jens Axboe <axboe@kernel.dk>,
Avi Shchislowski <Avi.Shchislowski@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
"Bean Huo (beanhuo)" <beanhuo@micron.com>,
Manjong Lee <mj0123.lee@samsung.com>,
"david@fromorbit.com" <david@fromorbit.com>
Cc: "hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"song@kernel.org" <song@kernel.org>,
"seunghwan.hyun@samsung.com" <seunghwan.hyun@samsung.com>,
"sookwan7.kim@samsung.com" <sookwan7.kim@samsung.com>,
"nanich.lee@samsung.com" <nanich.lee@samsung.com>,
"woosung2.lee@samsung.com" <woosung2.lee@samsung.com>,
"yt0928.kim@samsung.com" <yt0928.kim@samsung.com>,
"junho89.kim@samsung.com" <junho89.kim@samsung.com>,
"jisoo2146.oh@samsung.com" <jisoo2146.oh@samsung.com>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: RE: [EXT] Re: [PATCH 2/2] block: remove the per-bio/request write hint.
Date: Tue, 15 Mar 2022 15:36:30 +0000 [thread overview]
Message-ID: <CO3PR08MB7975EF4B014E211ACFAB7AF4DC109@CO3PR08MB7975.namprd08.prod.outlook.com> (raw)
In-Reply-To: <0c40073d-3920-8835-fc50-b17d4da099f0@kernel.dk>
>
> This isn't some setup to solicit votes on who supports what. If the code isn't
> upstream, it by definition doesn't exist to the kernel. No amount of "we're
> also interested in this" changes that.
>
> What I wrote earlier still applies - whoever is interested in supporting lifetime
> hints should submit that code upstream. The existing patchset to clean this
> up doesn't change that process AT ALL. As mentioned, the only difference is
> what the baseline looks like in terms of what the patchset is based on.
>
Jens,
Actually we might work to issue a patch and revert the patch plus add the code
that Bean and Bart mentioned which is currently Android only.
The reason it has not been done before is because for now it's not production yet
but it may soon be that case.
Would this patch revert be an option and accepted as a closure for this discussion?
Another option (which I actually prefer), if I ask for a MM & Storage BoF discussion
on storage hints where I can show you the status of temperature management
and my studies on how this is beneficial for storage devices.
Would this be more beneficial and maybe get some wider consensus
on the write hints?
After that consensus reverting (or agreeing on a new approach) will be easier.
> --
> Jens Axboe
Cheers,
Luca
next prev parent reply other threads:[~2022-03-15 15:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 17:55 [PATCH 1/2] nvme: remove support or stream based temperature hint Christoph Hellwig
2022-03-04 17:55 ` [PATCH 2/2] block: remove the per-bio/request write hint Christoph Hellwig
2022-03-04 19:24 ` Jens Axboe
2022-03-04 22:12 ` Dave Chinner
2022-03-05 5:19 ` Christoph Hellwig
2022-03-05 6:09 ` Number of parity disks Kengo.M
2022-03-05 8:56 ` Piergiorgio Sartor
2022-03-05 21:40 ` [PATCH 2/2] block: remove the per-bio/request write hint Dave Chinner
2022-03-05 23:55 ` Bart Van Assche
2022-03-06 17:11 ` Jens Axboe
2022-03-06 18:01 ` Christoph Hellwig
2022-03-06 18:06 ` Jens Axboe
2022-03-06 23:17 ` Dave Chinner
[not found] ` <CGME20220309042324epcas1p111312e20f4429dc3a17172458284a923@epcas1p1.samsung.com>
2022-03-09 13:31 ` Manjong Lee
2022-03-09 8:24 ` Paul Menzel
2022-03-10 11:34 ` [EXT] " Luca Porzio (lporzio)
2022-03-10 12:15 ` Jens Axboe
2022-03-10 18:50 ` Luca Porzio (lporzio)
2022-03-10 19:10 ` Jens Axboe
2022-03-10 19:34 ` Bart Van Assche
2022-03-10 21:52 ` Bean Huo (beanhuo)
2022-03-10 22:10 ` Jens Axboe
2022-03-11 16:45 ` Bart Van Assche
2022-03-11 16:56 ` Jens Axboe
2022-03-14 7:40 ` Avi Shchislowski
2022-03-14 8:00 ` hch
2022-03-14 19:50 ` Eric Biggers
2022-03-14 19:58 ` [EXT] " Jens Axboe
2022-03-15 15:36 ` Luca Porzio (lporzio) [this message]
2022-03-15 15:44 ` Jens Axboe
2022-03-10 22:18 ` Bart Van Assche
2022-03-11 5:31 ` Eric Biggers
2022-03-11 5:31 ` [f2fs-dev] " Eric Biggers
2022-03-11 9:21 ` Luca Porzio (lporzio)
2022-03-10 14:21 ` hch
2022-03-10 18:51 ` Luca Porzio (lporzio)
2022-03-10 19:14 ` hch
2022-03-11 5:06 ` Eric Biggers
2022-03-11 9:23 ` Luca Porzio (lporzio)
2022-03-04 19:34 ` [PATCH 1/2] nvme: remove support or stream based temperature hint Keith Busch
2022-03-04 19:36 ` Christoph Hellwig
2022-03-04 19:38 ` Jens Axboe
2022-03-04 20:20 ` 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=CO3PR08MB7975EF4B014E211ACFAB7AF4DC109@CO3PR08MB7975.namprd08.prod.outlook.com \
--to=lporzio@micron.com \
--cc=Avi.Shchislowski@wdc.com \
--cc=axboe@kernel.dk \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=jisoo2146.oh@samsung.com \
--cc=junho89.kim@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=mj0123.lee@samsung.com \
--cc=nanich.lee@samsung.com \
--cc=sagi@grimberg.me \
--cc=seunghwan.hyun@samsung.com \
--cc=song@kernel.org \
--cc=sookwan7.kim@samsung.com \
--cc=woosung2.lee@samsung.com \
--cc=yt0928.kim@samsung.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 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.