From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>,
kbusch@kernel.org, axboe@kernel.dk, brauner@kernel.org,
josef@toxicpanda.com, jack@suse.cz, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [RFC PATCH 2/5] fs: add the interface to query user write streams
Date: Wed, 22 Oct 2025 10:01:10 +0200 [thread overview]
Message-ID: <20251022080110.GA9997@lst.de> (raw)
In-Reply-To: <4cf4ebdd-a33f-4ff5-8016-aff8a6a87c54@samsung.com>
On Thu, Oct 16, 2025 at 03:27:22PM +0530, Kanchan Joshi wrote:
> On 8/12/2025 1:52 PM, Christoph Hellwig wrote:
> > On Tue, Jul 29, 2025 at 08:21:32PM +0530, Kanchan Joshi wrote:
> >> Add new fcntl F_GET_MAX_WRITE_STREAMS.
> >> This returns the numbers of streams that are available for userspace.
> >>
> >> And for that, use ->user_write_streams() callback when the involved
> >> filesystem provides it.
> >> In absence of such callback, use 'max_write_streams' queue limit of the
> >> underlying block device.
> > As mentioned in patch 1, I think we'd rather dispath the whole fcntl
> > to the file system, and then use generic helpers, which will give
> > more control of the details to the file system.
>
>
> I could not follow it, can you please expand that a bit.
> Should I get F_GET_MAX_WRITE_STREAMS dispatched to new inode operation.
Handle all of F_GET_MAX_WRITE_STREAMS in the file system and add a new
file operation for it.
next prev parent reply other threads:[~2025-10-22 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250729145331epcas5p4821f0ddedbbe425b733bf8330878cb3d@epcas5p4.samsung.com>
2025-07-29 14:51 ` [RFC PATCH 0/5] FDP file I/O Kanchan Joshi
2025-07-29 14:51 ` [RFC PATCH 1/5] fs: add a new user_write_streams() callback Kanchan Joshi
2025-08-12 8:21 ` Christoph Hellwig
2025-07-29 14:51 ` [RFC PATCH 2/5] fs: add the interface to query user write streams Kanchan Joshi
2025-07-30 4:28 ` kernel test robot
2025-08-12 8:22 ` Christoph Hellwig
2025-10-16 9:57 ` Kanchan Joshi
2025-10-22 8:01 ` Christoph Hellwig [this message]
2025-07-29 14:51 ` [RFC PATCH 3/5] fs: add a write stream field to the inode Kanchan Joshi
2025-08-12 8:23 ` Christoph Hellwig
2025-07-29 14:51 ` [RFC PATCH 4/5] fs: propagate write stream Kanchan Joshi
2025-08-12 8:24 ` Christoph Hellwig
2025-10-16 9:47 ` Kanchan Joshi
2025-10-22 8:02 ` Christoph Hellwig
2025-07-29 14:51 ` [RFC PATCH 5/5] fs: add set and query " 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=20251022080110.GA9997@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@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 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.