From: Andreas Hindborg <nmi@metaspace.dk>
To: "Matias Bjørling" <Matias.Bjorling@wdc.com>
Cc: "Ming Lei" <ming.lei@redhat.com>,
"Viacheslav A.Dubeyko" <viacheslav.dubeyko@bytedance.com>,
"Viacheslav Dubeyko" <slava@dubeyko.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Linux FS Devel" <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"Javier González" <javier.gonz@samsung.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
"Adam Manzanares" <a.manzanares@samsung.com>,
"Hans Holmberg" <Hans.Holmberg@wdc.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"Andreas Hindborg" <a.hindborg@samsung.com>
Subject: Re: [External] [LSF/MM/BPF BoF] Session for Zoned Storage 2023
Date: Mon, 30 Jan 2023 12:24:20 +0100 [thread overview]
Message-ID: <87pmawuu7b.fsf@metaspace.dk> (raw)
In-Reply-To: <BN8PR04MB64170AF4B399B6A3E26BAAC6F1D39@BN8PR04MB6417.namprd04.prod.outlook.com>
Hi Ming, Matias,
Matias Bjørling <Matias.Bjorling@wdc.com> writes:
<snip>
>> >
>> > I think we can consider such discussions:
>> > (1) I assume that we still need to discuss PO2 zone sizes?
>> > (2) Status of ZNS SSD support in F2FS, btrfs (maybe, bcachefs and
>> > other file systems)
>> > (3) Any news from ZoneFS (+ ZenFS maybe)?
>> > (4) New ZNS standard features that we need to support on block layer + FS
>> levels?
>> > (5) ZNS drive emulation + additional testing features?
>>
>> ZNS drive emulation can be done as one ublk target(userspace implementation
>> with ublk driver extension), and it was discussed before:
>>
>> https://github.com/ming1/ubdsrv/pull/28
>>
>>
>> Thanks,
>> Ming
>
> Hi Ming,
>
> Andreas recently transitioned from WD to another company. I am not sure if he'll continue this specific work, if he isn’t, my team will pick it up. It already looks very promising.
>
> Thanks, Matias
I joined Samsung recently, and I plan to continue the work on adding
zoned storage support to ublk in that context.
I will send the patches to the relevant lists when they get further
along. I hope your team will evaluate and provide feedback Matias :)
Best regards,
Andreas
next prev parent reply other threads:[~2023-01-30 11:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 19:17 [LSF/MM/BPF BoF] Session for Zoned Storage 2023 Viacheslav Dubeyko
2023-01-06 19:18 ` Luis Chamberlain
2023-01-06 19:30 ` Viacheslav Dubeyko
2023-01-07 1:56 ` [External] " Viacheslav A.Dubeyko
[not found] ` <20230109153315.waqfokse4srv6xlz@mpHalley-2.localdomain>
2023-01-09 17:05 ` Bart Van Assche
2023-01-09 19:11 ` Viacheslav A.Dubeyko
2023-01-09 22:53 ` Damien Le Moal
2023-01-09 23:00 ` Jens Axboe
2023-01-09 23:20 ` Viacheslav A.Dubeyko
2023-01-09 23:32 ` Damien Le Moal
2023-01-10 1:09 ` Jens Axboe
2023-01-10 1:39 ` Viacheslav A.Dubeyko
2023-01-10 1:50 ` Jens Axboe
2023-01-28 11:34 ` Ming Lei
[not found] ` <BN8PR04MB64170AF4B399B6A3E26BAAC6F1D39@BN8PR04MB6417.namprd04.prod.outlook.com>
2023-01-30 11:24 ` Andreas Hindborg [this message]
2023-01-06 22:18 ` Viacheslav A.Dubeyko
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=87pmawuu7b.fsf@metaspace.dk \
--to=nmi@metaspace.dk \
--cc=Hans.Holmberg@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=a.hindborg@samsung.com \
--cc=a.manzanares@samsung.com \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=javier.gonz@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=ming.lei@redhat.com \
--cc=slava@dubeyko.com \
--cc=viacheslav.dubeyko@bytedance.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.