From: "Javier González" <javier@javigon.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
"Keith Busch" <kbusch@kernel.org>,
"James Bottomley" <James.Bottomley@hansenpartnership.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Dave Chinner" <david@fromorbit.com>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
lsf-pc@lists.linux-foundation.org,
"Matias Bjørling" <matias.bjorling@wdc.com>,
"Damien Le Moal" <damien.lemoal@wdc.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Adam Manzanares" <a.manzanares@samsung.com>,
"Keith Busch" <keith.busch@wdc.com>,
"Johannes Thumshirn" <johannes.thumshirn@wdc.com>,
"Naohiro Aota" <naohiro.aota@wdc.com>,
"Pankaj Raghav" <pankydev8@gmail.com>,
"Kanchan Joshi" <joshi.k@samsung.com>,
"Nitesh Shetty" <nj.shetty@samsung.com>
Subject: Re: [LSF/MM/BPF BoF] BoF for Zoned Storage
Date: Fri, 11 Mar 2022 08:53:17 +0100 [thread overview]
Message-ID: <20220311075317.fjn3mj25dpicnpgi@ArmHalley.local> (raw)
In-Reply-To: <Yir9a8HusXWApk5l@infradead.org>
On 10.03.2022 23:42, Christoph Hellwig wrote:
>On Fri, Mar 11, 2022 at 04:39:12PM +0900, Damien Le Moal wrote:
>> > (we need to look into it). F2FS will use the emulation layer for now;
>> > only !PO2 devices will pay the price. We will add a knob in the block
>> > layer so that F2FS can force enable the emulation.
>>
>> No. The FS has no business changing the device.
Ok. Then it can be something the user can set.
>
>And nvme will not support any kind of emulation if that wasn't clear.
How do you propose we meed the request from Damien to support _all_
existing users if we remove the PO2 constraint from the block layer?
The emulation is not the goal, but it seems to be a requirement
next prev parent reply other threads:[~2022-03-11 7:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 0:56 [LSF/MM/BPF BoF] BoF for Zoned Storage Luis Chamberlain
2022-03-03 1:03 ` Luis Chamberlain
2022-03-03 1:33 ` Bart Van Assche
2022-03-03 4:31 ` Matias Bjørling
2022-03-03 5:21 ` Adam Manzanares
2022-03-03 5:32 ` Javier González
2022-03-03 6:29 ` Javier González
2022-03-03 7:54 ` Pankaj Raghav
2022-03-03 9:49 ` Damien Le Moal
2022-03-03 14:55 ` Adam Manzanares
2022-03-03 15:22 ` Damien Le Moal
2022-03-03 17:10 ` Adam Manzanares
2022-03-03 19:51 ` Matias Bjørling
2022-03-03 20:18 ` Adam Manzanares
2022-03-03 21:08 ` Javier González
2022-03-03 21:33 ` Matias Bjørling
2022-03-04 20:12 ` Luis Chamberlain
2022-03-06 23:54 ` Damien Le Moal
2022-03-03 16:12 ` Himanshu Madhani
2022-03-03 7:21 ` Hannes Reinecke
2022-03-03 8:55 ` Damien Le Moal
2022-03-03 7:38 ` Kanchan Joshi
2022-03-03 8:43 ` Johannes Thumshirn
2022-03-03 18:20 ` Viacheslav Dubeyko
2022-03-04 0:10 ` Dave Chinner
2022-03-04 22:10 ` Luis Chamberlain
2022-03-04 22:42 ` Dave Chinner
2022-03-04 22:55 ` Luis Chamberlain
2022-03-05 7:33 ` Javier González
2022-03-07 7:12 ` Dave Chinner
2022-03-07 10:27 ` Matias Bjørling
2022-03-07 11:29 ` Javier González
2022-03-11 0:49 ` Luis Chamberlain
2022-03-11 6:07 ` Christoph Hellwig
2022-03-11 20:31 ` Luis Chamberlain
2022-03-07 13:55 ` James Bottomley
2022-03-07 14:35 ` Javier González
2022-03-07 15:15 ` Keith Busch
2022-03-07 15:28 ` Javier González
2022-03-07 20:42 ` Damien Le Moal
2022-03-11 7:21 ` Javier González
2022-03-11 7:39 ` Damien Le Moal
2022-03-11 7:42 ` Christoph Hellwig
2022-03-11 7:53 ` Javier González [this message]
2022-03-11 8:46 ` Christoph Hellwig
2022-03-11 8:59 ` Javier González
2022-03-12 8:03 ` Damien Le Moal
2022-03-07 0:07 ` Damien Le Moal
2022-03-06 23:56 ` Damien Le Moal
2022-03-07 15:44 ` Luis Chamberlain
2022-03-07 16:23 ` Johannes Thumshirn
2022-03-07 16:36 ` Luis Chamberlain
2022-03-15 18:08 ` [EXT] " Luca Porzio (lporzio)
2022-03-15 18:39 ` Bart Van Assche
2022-03-15 18:47 ` Bean Huo (beanhuo)
2022-03-15 18:49 ` Jens Axboe
2022-03-15 19:04 ` Bean Huo (beanhuo)
2022-03-15 19:16 ` Jens Axboe
2022-03-15 19:59 ` Bart Van Assche
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=20220311075317.fjn3mj25dpicnpgi@ArmHalley.local \
--to=javier@javigon.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=a.manzanares@samsung.com \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=johannes.thumshirn@wdc.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=keith.busch@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=matias.bjorling@wdc.com \
--cc=mcgrof@kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=nj.shetty@samsung.com \
--cc=pankydev8@gmail.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.