public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: [PATCH v3 8/8] Documentation: ABI: stable: document the zoned_qd1_writes attribute
Date: Fri, 27 Feb 2026 10:49:51 +0900	[thread overview]
Message-ID: <20260227014951.2327711-9-dlemoal@kernel.org> (raw)
In-Reply-To: <20260227014951.2327711-1-dlemoal@kernel.org>

Update the documentation file Documentation/ABI/stable/sysfs-block to
describe the zoned_qd1_writes sysfs queue attribute file.

Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
---
 Documentation/ABI/stable/sysfs-block | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block
index 09a9d4aca0fd..bc3056af5eb2 100644
--- a/Documentation/ABI/stable/sysfs-block
+++ b/Documentation/ABI/stable/sysfs-block
@@ -886,6 +886,21 @@ Description:
 		zone commands, they will be treated as regular block devices and
 		zoned will report "none".
 
+What:		/sys/block/<disk>/queue/zoned_qd1_writes
+Date:		January 2026
+Contact:	Damien Le Moal <dlemoal@kernel.org>
+Description:
+		[RW] zoned_qd1_writes indicates if write operations to a zoned
+		block device are being handled using a single issuer context (a
+		kernel thread) operating at a maximum queue depth of 1. A value
+		of 0 is always reported for regular block devices and for zoned
+		block devices that are not rotational devices (e.g. ZNS SSDs or
+		zoned UFS devices). For rotational zoned block devices (e.g. SMR
+		HDDs) the default value is 1. Since this default may not be
+		appropriate for some devices, e.g. remotely connected devices
+		over high latency networks, the user can disable this feature by
+		setting this attribute to 0.
+
 
 What:		/sys/block/<disk>/hidden
 Date:		March 2023
-- 
2.53.0


  parent reply	other threads:[~2026-02-27  1:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  1:49 [PATCH v3 0/8] Improve zoned (SMR) HDD write throughput Damien Le Moal
2026-02-27  1:49 ` [PATCH v3 1/8] block: fix zone write plug removal Damien Le Moal
2026-02-27  9:22   ` Johannes Thumshirn
2026-02-27  9:40     ` Damien Le Moal
2026-02-27  9:44       ` Johannes Thumshirn
2026-02-27 13:48   ` Christoph Hellwig
2026-03-02  7:20   ` Hannes Reinecke
2026-02-27  1:49 ` [PATCH v3 2/8] block: fix zone write plugs refcount handling in disk_zone_wplug_schedule_bio_work() Damien Le Moal
2026-02-27  9:23   ` Johannes Thumshirn
2026-03-02  7:21   ` Hannes Reinecke
2026-02-27  1:49 ` [PATCH v3 3/8] block: rename and simplify disk_get_and_lock_zone_wplug() Damien Le Moal
2026-02-27  9:32   ` Johannes Thumshirn
2026-02-27 13:48   ` Christoph Hellwig
2026-03-02  7:22   ` Hannes Reinecke
2026-02-27  1:49 ` [PATCH v3 4/8] block: remove disk_zone_is_full() Damien Le Moal
2026-02-27  1:49 ` [PATCH v3 5/8] block: rename struct gendisk zone_wplugs_lock field Damien Le Moal
2026-02-27  1:49 ` [PATCH v3 6/8] block: allow submitting all zone writes from a single context Damien Le Moal
2026-02-27  9:41   ` Johannes Thumshirn
2026-03-02  7:23   ` Hannes Reinecke
2026-02-27  1:49 ` [PATCH v3 7/8] block: default to QD=1 writes for blk-mq rotational zoned devices Damien Le Moal
2026-02-27  9:48   ` Johannes Thumshirn
2026-02-27  1:49 ` Damien Le Moal [this message]
2026-02-27  9:51   ` [PATCH v3 8/8] Documentation: ABI: stable: document the zoned_qd1_writes attribute Johannes Thumshirn

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=20260227014951.2327711-9-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@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