From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: brauner@kernel.org, hch@lst.de, djwong@kernel.org, jack@suse.cz,
cem@kernel.org, kbusch@kernel.org, axboe@kernel.dk,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
gost.dev@samsung.com, Hans Holmberg <hans.holmberg@wdc.com>
Subject: Re: [PATCH v2 0/5] write streams and xfs spatial isolation
Date: Mon, 9 Mar 2026 16:40:47 +0100 [thread overview]
Message-ID: <20260309154047.GA18538@lst.de> (raw)
In-Reply-To: <20260309052944.156054-1-joshi.k@samsung.com>
This is laking numbers to justify all the changes.
From previous experiments the most important isolations is to put
the file system log and metadata into a separate stream each, which
would be the first step before exposing user knobs.
And once we look into application optimizations I think your best bet is
to resurrect the FDP/write streams support for zoned XFS that Hans and I
did and posted in reply to one of Keith' iterations of the write stream
patches. This will reuse all the intelligent placement decisions we've
put into that allocator. Once that is done we can look into exposing the
write streams already inherent in that to user space, but we really
should be doing all the ground work first. And maybe some of this can
apply to the conventional allocator, but given that it has no way to
track the placement unit sizes I'm a bit doubtful that the results will
look great.
next prev parent reply other threads:[~2026-03-09 15:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260309053425epcas5p32886580a4fbe646ceee66f2864970e9f@epcas5p3.samsung.com>
2026-03-09 5:29 ` [PATCH v2 0/5] write streams and xfs spatial isolation Kanchan Joshi
2026-03-09 5:29 ` [PATCH v2 1/5] fs: add generic write-stream management ioctl Kanchan Joshi
2026-03-09 16:33 ` Darrick J. Wong
2026-03-10 17:55 ` Kanchan Joshi
2026-03-10 20:44 ` Darrick J. Wong
2026-03-09 5:29 ` [PATCH v2 2/5] iomap: introduce and propagate write_stream Kanchan Joshi
2026-03-09 16:34 ` Darrick J. Wong
2026-03-10 17:58 ` Kanchan Joshi
2026-03-09 5:29 ` [PATCH v2 3/5] xfs: implement write-stream management support Kanchan Joshi
2026-03-09 16:38 ` Darrick J. Wong
2026-03-10 18:07 ` Kanchan Joshi
2026-03-09 5:29 ` [PATCH v2 4/5] xfs: steer allocation using write stream Kanchan Joshi
2026-03-09 12:45 ` kernel test robot
2026-03-09 20:01 ` kernel test robot
2026-03-10 5:47 ` Dave Chinner
2026-03-10 19:03 ` Kanchan Joshi
2026-03-10 22:44 ` Dave Chinner
2026-03-11 9:59 ` Kanchan Joshi
2026-03-09 5:29 ` [PATCH v2 5/5] xfs: introduce software write streams Kanchan Joshi
2026-03-10 6:01 ` Dave Chinner
2026-03-09 15:40 ` Christoph Hellwig [this message]
2026-03-10 21:19 ` [PATCH v2 0/5] write streams and xfs spatial isolation Kanchan Joshi
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=20260309154047.GA18538@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hans.holmberg@wdc.com \
--cc=jack@suse.cz \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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