From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, clm@meta.com, axboe@kernel.dk,
shr@devkernel.io, akpm@linux-foundation.org
Subject: [merged mm-stable] mm-document-sys-class-bdi-bdi-strict_limit-knob.patch removed from -mm tree
Date: Wed, 30 Nov 2022 16:02:45 -0800 [thread overview]
Message-ID: <20221201000246.2F4BDC433D7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: document /sys/class/bdi/<bdi>/strict_limit knob
has been removed from the -mm tree. Its filename was
mm-document-sys-class-bdi-bdi-strict_limit-knob.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Stefan Roesch <shr@devkernel.io>
Subject: mm: document /sys/class/bdi/<bdi>/strict_limit knob
Date: Fri, 18 Nov 2022 16:51:58 -0800
This documents the new /sys/class/bdi/<bdi>/strict_limit knob.
Link: https://lkml.kernel.org/r/20221119005215.3052436-4-shr@devkernel.io
Signed-off-by: Stefan Roesch <shr@devkernel.io>
Cc: Chris Mason <clm@meta.com>
Cc: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
Documentation/ABI/testing/sysfs-class-bdi | 11 +++++++++++
1 file changed, 11 insertions(+)
--- a/Documentation/ABI/testing/sysfs-class-bdi~mm-document-sys-class-bdi-bdi-strict_limit-knob
+++ a/Documentation/ABI/testing/sysfs-class-bdi
@@ -56,6 +56,17 @@ Description:
be trusted to play fair.
(read-write)
+What: /sys/class/bdi/<bdi>/strict_limit
+Date: October 2022
+Contact: Stefan Roesch <shr@devkernel.io>
+Description:
+ Forces per-BDI checks for the share of given device in the write-back
+ cache even before the global background dirty limit is reached. This
+ is useful in situations where the global limit is much higher than
+ affordable for given relatively slow (or untrusted) device. Turning
+ strictlimit on has no visible effect if max_ratio is equal to 100%.
+
+ (read-write)
What: /sys/class/bdi/<bdi>/stable_pages_required
Date: January 2008
Contact: Peter Zijlstra <a.p.zijlstra@chello.nl>
_
Patches currently in -mm which might be from shr@devkernel.io are
reply other threads:[~2022-12-01 0:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221201000246.2F4BDC433D7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=clm@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=shr@devkernel.io \
/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.