From: Ming Lei <ming.lei@redhat.com>
To: "Viacheslav A.Dubeyko" <viacheslav.dubeyko@bytedance.com>
Cc: "Viacheslav Dubeyko" <slava@dubeyko.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Linux FS Devel" <linux-fsdevel@vger.kernel.org>,
linux-block@vger.kernel.org,
"Javier González" <javier.gonz@samsung.com>,
"Matias Bjørling" <Matias.Bjorling@wdc.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, andreas@metaspace.dk
Subject: Re: [External] [LSF/MM/BPF BoF] Session for Zoned Storage 2023
Date: Sat, 28 Jan 2023 19:34:22 +0800 [thread overview]
Message-ID: <Y9UIPsp479CysMmX@T590> (raw)
In-Reply-To: <5DF10459-88F3-48DA-AEB2-5B436549A194@bytedance.com>
On Fri, Jan 06, 2023 at 05:56:24PM -0800, Viacheslav A.Dubeyko wrote:
>
>
> > On Jan 6, 2023, at 11:30 AM, Viacheslav Dubeyko <slava@dubeyko.com> wrote:
> >
> >
> >
> >> On Jan 6, 2023, at 11:18 AM, Luis Chamberlain <mcgrof@kernel.org> wrote:
> >>
> >> On Fri, Jan 06, 2023 at 11:17:19AM -0800, Viacheslav Dubeyko wrote:
> >>> Hello,
> >>>
> >>> As far as I can see, I have two topics for discussion.
> >>
> >> What's that?
> >
> > I am going to share these topics in separate emails. :)
> >
> > (1) I am going to share SSDFS patchset soon. And topic is:
> > SSDFS + ZNS SSD: deterministic architecture decreasing TCO cost of data infrastructure.
> >
> > (2) Second topic is:
> > How to achieve better lifetime and performance of caching layer with ZNS SSD?
> >
>
> 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
next prev parent reply other threads:[~2023-01-28 11:35 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 [this message]
[not found] ` <BN8PR04MB64170AF4B399B6A3E26BAAC6F1D39@BN8PR04MB6417.namprd04.prod.outlook.com>
2023-01-30 11:24 ` Andreas Hindborg
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=Y9UIPsp479CysMmX@T590 \
--to=ming.lei@redhat.com \
--cc=Matias.Bjorling@wdc.com \
--cc=a.manzanares@samsung.com \
--cc=andreas@metaspace.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hans.holmberg@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=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 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).