blk-mq: fix stale nr_requests documentation

The nr_requests documentation is still the removed single queue, remove
it and update to current blk-mq.

Signed-off-by: Yu Kuai <yukuai3@huawei.com>
Reviewed-by: Nilay Shroff <nilay@linux.ibm.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>

diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block
index 0ddffc9133d04d65c30dd62ba5c6535a1a3779f6..0ed10aeff86b86d6cc9389aaa896afb6e2868ca0 100644 (file)
--- a/Documentation/ABI/stable/sysfs-block
+++ b/Documentation/ABI/stable/sysfs-block
@@ -603,16 +603,10 @@ Date:             July 2003
 Contact:       linux-block@vger.kernel.org
 Description:
                [RW] This controls how many requests may be allocated in the
-               block layer for read or write requests. Note that the total
-               allocated number may be twice this amount, since it applies only
-               to reads or writes (not the accumulated sum).
-
-               To avoid priority inversion through request starvation, a
-               request queue maintains a separate request pool per each cgroup
-               when CONFIG_BLK_CGROUP is enabled, and this parameter applies to
-               each such per-block-cgroup request pool.  IOW, if there are N
-               block cgroups, each request queue may have up to N request
-               pools, each independently regulated by nr_requests.
+               block layer. Noted this value only represents the quantity for a
+               single blk_mq_tags instance. The actual number for the entire
+               device depends on the hardware queue count, whether elevator is
+               enabled, and whether tags are shared.
 
 
 What:          /sys/block/<disk>/queue/nr_zones