Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: brauner@kernel.org, hch@lst.de, djwong@kernel.org,
	dgc@kernel.org, jack@suse.cz, cem@kernel.org, axboe@kernel.dk,
	kbusch@kernel.org, ritesh.list@gmail.com,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-block@vger.kernel.org, gost.dev@samsung.com,
	Anuj Gupta <anuj20.g@samsung.com>
Subject: Re: [PATCH v4 6/6] xfs: introduce software write streams
Date: Wed, 19 Aug 2026 09:31:13 +0200	[thread overview]
Message-ID: <20260819073113.GB2332@lst.de> (raw)
In-Reply-To: <20260717125538.508925-7-joshi.k@samsung.com>

On Fri, Jul 17, 2026 at 06:25:38PM +0530, Kanchan Joshi wrote:
> Even when the underlying block device does not advertise write streams,
> XFS can choose do so, as that enables logical spatial isolation and
> dynamic AG-set based concurrency for the standard storage, excluding
> rtvolume.

Ok, this gets back to my previous point.  Pleadse just ignore the
hardware write streams in the initial patch, and then add the aligning
to hardware write streams later.

> +	nr_streams = bdev_max_write_streams(bdev);
> +	if (nr_streams > 0)
> +		return nr_streams;
> +	/*
> +	 * Enable software-only streams if hardware streams are not available.
> +	 * This helps to
> +	 * - improve isolation; reduce allocation interleaving.
> +	 * - improve concurrency using AG-set based steering within and across streams.

Overly long line.

> +	 */
> +	nr_ags = mp->m_sb.sb_agcount;
> +	if (nr_ags >= 16)
> +		ag_set_size = 4;
> +	else if (nr_ags >= 8)
> +		ag_set_size = 2;
> +	else
> +		ag_set_size = 1;
> +	nr_streams = nr_ags / ag_set_size;
> +	return min_t(uint16_t, nr_streams, XFS_SW_WRITE_STREAMS_MAX);

.. and this value should be cached somewhere.

>  	nr_streams = bdev_max_write_streams(mp->m_ddev_targp->bt_bdev);
> -	if (nr_streams) {
> -		mp->m_streams_in_use = bitmap_zalloc(nr_streams, GFP_KERNEL);
> -		if (!mp->m_streams_in_use) {
> -			error = -ENOMEM;
> -			goto out_shutdown_devices;
> -		}
> +	if (!nr_streams)
> +		nr_streams = XFS_SW_WRITE_STREAMS_MAX;
> +	mp->m_streams_in_use = bitmap_zalloc(nr_streams, GFP_KERNEL);
> +	if (!mp->m_streams_in_use) {
> +		error = -ENOMEM;
> +		goto out_shutdown_devices;
>  	}

and also be used here?

While we're at it, the stream allocator should probably go into
the buftarg to prepare for also adding it for the RT volume.

      reply	other threads:[~2026-08-19  7:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20260717125624epcas5p3fefc5b8ff274260bf8fb2f1b225b4f9a@epcas5p3.samsung.com>
2026-07-17 12:55 ` [PATCH v4 0/6] xfs write streams Kanchan Joshi
2026-07-17 12:55   ` [PATCH v4 1/6] fs: add write-stream management ioctls Kanchan Joshi
2026-07-21  3:03     ` Darrick J. Wong
2026-07-30 14:52       ` Kanchan Joshi
2026-07-30 17:22         ` Darrick J. Wong
2026-07-31  8:15           ` Kanchan Joshi
2026-08-19  7:04           ` Christoph Hellwig
2026-08-19  7:08         ` Christoph Hellwig
2026-08-19  7:11     ` Christoph Hellwig
2026-07-17 12:55   ` [PATCH v4 2/6] iomap: introduce and propagate write_stream Kanchan Joshi
2026-08-19  7:09     ` Christoph Hellwig
2026-07-17 12:55   ` [PATCH v4 3/6] xfs: implement write-stream management support Kanchan Joshi
2026-07-21  3:08     ` Darrick J. Wong
2026-07-31  8:03       ` Kanchan Joshi
2026-08-19  7:12         ` Christoph Hellwig
2026-08-19  7:18     ` Christoph Hellwig
2026-08-19  7:24     ` Christoph Hellwig
2026-07-17 12:55   ` [PATCH v4 4/6] xfs: generic AG set based steering Kanchan Joshi
2026-07-21  3:20     ` Darrick J. Wong
2026-07-24 14:57       ` Kanchan Joshi
2026-08-19  7:21     ` Christoph Hellwig
2026-07-17 12:55   ` [PATCH v4 5/6] xfs: write stream based AG placement Kanchan Joshi
2026-08-19  7:29     ` Christoph Hellwig
2026-07-17 12:55   ` [PATCH v4 6/6] xfs: introduce software write streams Kanchan Joshi
2026-08-19  7:31     ` Christoph Hellwig [this message]

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=20260819073113.GB2332@lst.de \
    --to=hch@lst.de \
    --cc=anuj20.g@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=dgc@kernel.org \
    --cc=djwong@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=jack@suse.cz \
    --cc=joshi.k@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ritesh.list@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox