From: Eric Biggers <ebiggers@kernel.org>
To: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: linux-doc@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v3 5/8] docs: sysfs-block: document stable_writes
Date: Wed, 8 Dec 2021 16:38:30 -0800 [thread overview]
Message-ID: <20211209003833.6396-6-ebiggers@kernel.org> (raw)
In-Reply-To: <20211209003833.6396-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
/sys/block/<disk>/queue/stable_writes is completely undocumented.
Document it.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
Documentation/ABI/stable/sysfs-block | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block
index de3b86a3dfa55..288626e8cb532 100644
--- a/Documentation/ABI/stable/sysfs-block
+++ b/Documentation/ABI/stable/sysfs-block
@@ -516,6 +516,23 @@ Description:
scheduler module, if it isn't already present in the system.
+What: /sys/block/<disk>/queue/stable_writes
+Date: September 2020
+Contact: linux-block@vger.kernel.org
+Description:
+ [RW] This file will contain '1' if memory must not be modified
+ while it is being used in a write request to this device. When
+ this is the case and the kernel is performing writeback of a
+ page, the kernel will wait for writeback to complete before
+ allowing the page to be modified again, rather than allowing
+ immediate modification as is normally the case. This
+ restriction arises when the device accesses the memory multiple
+ times where the same data must be seen every time -- for
+ example, once to calculate a checksum and once to actually write
+ the data. If no such restriction exists, this file will contain
+ '0'. This file is writable for testing purposes.
+
+
What: /sys/block/<disk>/queue/throttle_sample_time
Date: March 2017
Contact: linux-block@vger.kernel.org
--
2.34.1
next prev parent reply other threads:[~2021-12-09 0:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 0:38 [PATCH v3 0/8] docs: consolidate sysfs-block into Documentation/ABI/ Eric Biggers
2021-12-09 0:38 ` [PATCH v3 1/8] docs: sysfs-block: move to stable directory Eric Biggers
2021-12-09 0:38 ` [PATCH v3 2/8] docs: sysfs-block: sort alphabetically Eric Biggers
2021-12-09 0:38 ` [PATCH v3 3/8] docs: sysfs-block: add contact for nomerges Eric Biggers
2021-12-09 0:38 ` [PATCH v3 4/8] docs: sysfs-block: fill in missing documentation from queue-sysfs.rst Eric Biggers
2021-12-09 0:38 ` Eric Biggers [this message]
2021-12-09 0:38 ` [PATCH v3 6/8] docs: sysfs-block: document virt_boundary_mask Eric Biggers
2021-12-09 0:38 ` [PATCH v3 7/8] docs: block: remove queue-sysfs.rst Eric Biggers
2021-12-09 0:38 ` [PATCH v3 8/8] MAINTAINERS: add entries for block layer documentation Eric Biggers
2021-12-21 15:41 ` [PATCH v3 0/8] docs: consolidate sysfs-block into Documentation/ABI/ Eric Biggers
2022-01-03 15:06 ` Eric Biggers
2022-01-06 21:41 ` Eric Biggers
2022-01-07 20:58 ` Bart Van Assche
2022-01-09 17:01 ` Jens Axboe
2022-01-09 21:25 ` Eric Biggers
2022-01-10 1:58 ` Jens Axboe
2022-01-11 0:37 ` Jonathan Corbet
2022-01-10 1:59 ` Jens Axboe
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=20211209003833.6396-6-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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.