From patchwork Fri Jun 28 20:07:42 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bart Van Assche X-Patchwork-Id: 11023445 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 6BBA0746 for ; Fri, 28 Jun 2019 20:07:57 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 6980F287B7 for ; Fri, 28 Jun 2019 20:07:57 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 5C67D287BE; Fri, 28 Jun 2019 20:07:57 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id E81DD287B7 for ; Fri, 28 Jun 2019 20:07:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727069AbfF1UH4 (ORCPT ); Fri, 28 Jun 2019 16:07:56 -0400 Received: from mail-pl1-f195.google.com ([209.85.214.195]:41589 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726809AbfF1UH4 (ORCPT ); Fri, 28 Jun 2019 16:07:56 -0400 Received: by mail-pl1-f195.google.com with SMTP id m7so3819367pls.8 for ; Fri, 28 Jun 2019 13:07:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=BbPCld27i5b7rRPlkqpOl7AnJoTAFBIz3QGKk54uvC8=; b=LHRK2yFiaACvZgnk/OFTXKXdnD7taI/bA5RhVU5wgBNCooP/84ZbTcNnYXj8rxAcKz iQbxp3ANfds0VLdO7Tt3moC1e5slRaS14UeBlWYYB19WfAah9hTaM2TiXWlLJgbWyqRg GFYk2BLkPWL0jutDI9zulQO2Y1lEWvGXIo5vC1rWCQMjGWNiQmQJTRc+gHSTteeVuehE c0dnIjhWBpSpSd4eLqIHeazotsxDY/gVEpCRqsUwtOmEWyHOscSJRyfjW97ri6YqPLIO UhA5U07rHWJ/ag1sJ62PaJ95igUMOr+yBHIa8vC/oOTzvVttMbhqhrhfgJ2Lc4kJZ3AK yfsg== X-Gm-Message-State: APjAAAWXIL7MKymJyW198ZMjBZUhQj+9iOXE/ywGgawRj6c6xXUa9XVH ERnrv6VlfN06ODfMUUK+DMn320Q71mU= X-Google-Smtp-Source: APXvYqyBCQ0p0jyi/PIdlPv+Q/UfJVfgOJ6HvlrJKEPazO46COqn0jWsYnYPldjQxkgOHJI4deMKnQ== X-Received: by 2002:a17:902:8b88:: with SMTP id ay8mr13276469plb.139.1561752475617; Fri, 28 Jun 2019 13:07:55 -0700 (PDT) Received: from desktop-bart.svl.corp.google.com ([2620:15c:2cd:202:4308:52a3:24b6:2c60]) by smtp.gmail.com with ESMTPSA id 65sm1186010pff.148.2019.06.28.13.07.54 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 28 Jun 2019 13:07:54 -0700 (PDT) From: Bart Van Assche To: Jens Axboe Cc: linux-block@vger.kernel.org, Christoph Hellwig , Bart Van Assche Subject: [PATCH 1/4] block, documentation: Fix wbt_lat_usec documentation Date: Fri, 28 Jun 2019 13:07:42 -0700 Message-Id: <20190628200745.206110-2-bvanassche@acm.org> X-Mailer: git-send-email 2.22.0.410.gd8fdbe21b5-goog In-Reply-To: <20190628200745.206110-1-bvanassche@acm.org> References: <20190628200745.206110-1-bvanassche@acm.org> MIME-Version: 1.0 Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Fix the spelling of the wbt_lat_usec sysfs attribute. Fixes: 87760e5eef35 ("block: hook up writeback throttling") # v4.10. Signed-off-by: Bart Van Assche Reviewed-by: Martin K. Petersen --- Documentation/block/queue-sysfs.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/block/queue-sysfs.txt b/Documentation/block/queue-sysfs.txt index 83b457e24bba..3eaf86806621 100644 --- a/Documentation/block/queue-sysfs.txt +++ b/Documentation/block/queue-sysfs.txt @@ -185,8 +185,8 @@ This is the number of bytes the device can write in a single write-same command. A value of '0' means write-same is not supported by this device. -wb_lat_usec (RW) ----------------- +wbt_lat_usec (RW) +----------------- If the device is registered for writeback throttling, then this file shows the target minimum read latency. If this latency is exceeded in a given window of time (see wb_window_usec), then the writeback throttling will start From patchwork Fri Jun 28 20:07:43 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bart Van Assche X-Patchwork-Id: 11023447 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id E6290746 for ; Fri, 28 Jun 2019 20:07:58 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id E408E28714 for ; Fri, 28 Jun 2019 20:07:58 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id D8698287B8; Fri, 28 Jun 2019 20:07:58 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 7352828714 for ; Fri, 28 Jun 2019 20:07:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727068AbfF1UH6 (ORCPT ); Fri, 28 Jun 2019 16:07:58 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:35754 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726809AbfF1UH5 (ORCPT ); Fri, 28 Jun 2019 16:07:57 -0400 Received: by mail-pg1-f193.google.com with SMTP id s27so3064922pgl.2 for ; Fri, 28 Jun 2019 13:07:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=ystmvT3hcHG5GcUUUJ7CBMWhBvBULg4zwoaXWWT5Oy0=; b=XSz6Nxpr6Xq9xGHXu4548I/e92oA43vkqz9ePcNnqUfgPTDug01Kk6KUI3YqCVI+Ac hsyHbZRk3RXaltgTWfgEUGr0DqvX6k14nCSsjHU0qMtCwUmNAli1iMbhvvxb8nxLM/5S +2vKy9WOoFmqcP4nW0TxsPf2Yxf9zU5dKLb/bs44u09SD/Wfqo86eE9TjMkeritt8fcc mRyTuUlDlzbMGgfCZxb7OM0eFF+IyHzpfu4WKBA+3AVwkQu7jNl0VXxl6D/p4DpSQHOb sDm9KPAJBnfkX8DyrgBiV6AQQfkqJhpTeN7W3ZKLMBZ8oEWYlw3AGTOugmE56+vOF7OQ K2/g== X-Gm-Message-State: APjAAAWR7EF+Dld30Tb7DX33M97bkfvtpR0r/A1w1WpAs5ytErHFY2yL v4gAIgcvayEqOtogW48V7ykfoucMRik= X-Google-Smtp-Source: APXvYqy8pFMNA0ND1tyaHpe1SFbWHAujdHfmTh9AQFryvR0m9wqOD3l5i2IDXIU3lYbyeEc/THQlOg== X-Received: by 2002:a63:2f44:: with SMTP id v65mr10752921pgv.185.1561752477045; Fri, 28 Jun 2019 13:07:57 -0700 (PDT) Received: from desktop-bart.svl.corp.google.com ([2620:15c:2cd:202:4308:52a3:24b6:2c60]) by smtp.gmail.com with ESMTPSA id 65sm1186010pff.148.2019.06.28.13.07.55 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 28 Jun 2019 13:07:55 -0700 (PDT) From: Bart Van Assche To: Jens Axboe Cc: linux-block@vger.kernel.org, Christoph Hellwig , Bart Van Assche , Damien Le Moal Subject: [PATCH 2/4] block, documentation: Sort queue sysfs attribute names alphabetically Date: Fri, 28 Jun 2019 13:07:43 -0700 Message-Id: <20190628200745.206110-3-bvanassche@acm.org> X-Mailer: git-send-email 2.22.0.410.gd8fdbe21b5-goog In-Reply-To: <20190628200745.206110-1-bvanassche@acm.org> References: <20190628200745.206110-1-bvanassche@acm.org> MIME-Version: 1.0 Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Commit f9824952ee1c ("block: update sysfs documentation") # v5.0 broke the alphabetical order of the sysfs attribute names. List queue sysfs attribute names alphabetically. Cc: Damien Le Moal Signed-off-by: Bart Van Assche Reviewed-by: Martin K. Petersen --- Documentation/block/queue-sysfs.txt | 30 ++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/Documentation/block/queue-sysfs.txt b/Documentation/block/queue-sysfs.txt index 3eaf86806621..f6da2efe2105 100644 --- a/Documentation/block/queue-sysfs.txt +++ b/Documentation/block/queue-sysfs.txt @@ -14,6 +14,15 @@ add_random (RW) This file allows to turn off the disk entropy contribution. Default value of this file is '1'(on). +chunk_sectors (RO) +------------------ +This has different meaning depending on the type of the block device. +For a RAID device (dm-raid), chunk_sectors indicates the size in 512B sectors +of the RAID volume stripe segment. For a zoned block device, either host-aware +or host-managed, chunk_sectors indicates the size in 512B sectors of the zones +of the device, with the eventual exception of the last zone of the device which +may be smaller. + dax (RO) -------- This file indicates whether the device supports Direct Access (DAX), @@ -132,6 +141,12 @@ 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. +nr_zones (RO) +------------- +For zoned block devices (zoned attribute indicating "host-managed" or +"host-aware"), this indicates the total number of zones of the device. +This is always 0 for regular block devices. + optimal_io_size (RO) -------------------- This is the optimal IO size reported by the device. @@ -213,19 +228,4 @@ devices are described in the ZBC (Zoned Block Commands) and ZAC do not support zone commands, they will be treated as regular block devices and zoned will report "none". -nr_zones (RO) -------------- -For zoned block devices (zoned attribute indicating "host-managed" or -"host-aware"), this indicates the total number of zones of the device. -This is always 0 for regular block devices. - -chunk_sectors (RO) ------------------- -This has different meaning depending on the type of the block device. -For a RAID device (dm-raid), chunk_sectors indicates the size in 512B sectors -of the RAID volume stripe segment. For a zoned block device, either host-aware -or host-managed, chunk_sectors indicates the size in 512B sectors of the zones -of the device, with the eventual exception of the last zone of the device which -may be smaller. - Jens Axboe , February 2009 From patchwork Fri Jun 28 20:07:44 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bart Van Assche X-Patchwork-Id: 11023449 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id C81C714C0 for ; Fri, 28 Jun 2019 20:08:01 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C254528714 for ; Fri, 28 Jun 2019 20:08:01 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id B6AE5287CB; Fri, 28 Jun 2019 20:08:01 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id DA20928714 for ; Fri, 28 Jun 2019 20:07:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727073AbfF1UH7 (ORCPT ); Fri, 28 Jun 2019 16:07:59 -0400 Received: from mail-pf1-f194.google.com ([209.85.210.194]:36421 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726809AbfF1UH7 (ORCPT ); Fri, 28 Jun 2019 16:07:59 -0400 Received: by mail-pf1-f194.google.com with SMTP id r7so3532254pfl.3 for ; Fri, 28 Jun 2019 13:07:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=YzjQUCzMMWqN95NqHm9kNlqyu4468/vZuxTyImQfx4A=; b=qfZADct3oIh4VkxDTjBlYLBnx2yf52hynP+j3AB+GAVNbxDmrR8Lmt3MMM09jcG/B8 TtukD7KHynd+4EurxMREbNX22R+gspFEbr1+BElADLsbFFFxX+aqtUVk2CP1h+qdzQid VJBTW9zd6ovtU/U0PRilgYzHjFbjmY9gt2FkLUdcW7kKXIJPmvXzxwruAotqEFQv3XVP Ia0AO/nQnvtYrRwVfPSoBiT+So/wcyCk3pcUsQZ/6J/GTj5Zce0sJIVItbfRNumqN5hT JD3N6fwVQaFec+TbL2Kr8FluOFEue7vj0aVizC++zAXYBMqH6mnqQS0MW1Iwb8y8FmQZ OM8w== X-Gm-Message-State: APjAAAWeDOrmyyBWBfFWtTYIWrWhkUo+k3cDpmGK70ghqZwIv++Ujexy yooMN9nfGEIduExg2FTkOd8= X-Google-Smtp-Source: APXvYqzfaCAwlcej9WZu2IQw1zaj9QNkZIHC0SFoF03PcPEguAzz4n11v4d/YLABd7jnQAbH6QHTMQ== X-Received: by 2002:a17:90a:3225:: with SMTP id k34mr15103389pjb.31.1561752478360; Fri, 28 Jun 2019 13:07:58 -0700 (PDT) Received: from desktop-bart.svl.corp.google.com ([2620:15c:2cd:202:4308:52a3:24b6:2c60]) by smtp.gmail.com with ESMTPSA id 65sm1186010pff.148.2019.06.28.13.07.57 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 28 Jun 2019 13:07:57 -0700 (PDT) From: Bart Van Assche To: Jens Axboe Cc: linux-block@vger.kernel.org, Christoph Hellwig , Bart Van Assche , "Martin K . Petersen" Subject: [PATCH 3/4] block, documentation: Explain the word 'segments' Date: Fri, 28 Jun 2019 13:07:44 -0700 Message-Id: <20190628200745.206110-4-bvanassche@acm.org> X-Mailer: git-send-email 2.22.0.410.gd8fdbe21b5-goog In-Reply-To: <20190628200745.206110-1-bvanassche@acm.org> References: <20190628200745.206110-1-bvanassche@acm.org> MIME-Version: 1.0 Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Several block layer users who are not kernel developers do not know that the word 'segment' refers to an element in a DMA scatter/gather list. Make the block layer documentation easier to understand by stating explicitly what the word 'segment' stands for. Cc: Martin K. Petersen Signed-off-by: Bart Van Assche Reviewed-by: Martin K. Petersen --- Documentation/block/queue-sysfs.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/Documentation/block/queue-sysfs.txt b/Documentation/block/queue-sysfs.txt index f6da2efe2105..1515dcf3dec4 100644 --- a/Documentation/block/queue-sysfs.txt +++ b/Documentation/block/queue-sysfs.txt @@ -98,8 +98,9 @@ This is the maximum number of kilobytes supported in a single data transfer. max_integrity_segments (RO) --------------------------- -When read, this file shows the max limit of integrity segments as -set by block layer which a hardware controller can handle. +Maximum number of elements in a DMA scatter/gather list with integrity +data that will be submitted by the block layer core to the associated +block driver. max_sectors_kb (RW) ------------------- @@ -109,11 +110,12 @@ size allowed by the hardware. max_segments (RO) ----------------- -Maximum number of segments of the device. +Maximum number of elements in a DMA scatter/gather list that is submitted +to the associated block driver. max_segment_size (RO) --------------------- -Maximum segment size of the device. +Maximum size in bytes of a single element in a DMA scatter/gather list. minimum_io_size (RO) -------------------- From patchwork Fri Jun 28 20:07:45 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bart Van Assche X-Patchwork-Id: 11023451 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id D84A315E6 for ; Fri, 28 Jun 2019 20:08:01 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id D4E0C287B7 for ; Fri, 28 Jun 2019 20:08:01 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id C97FD2883B; Fri, 28 Jun 2019 20:08:01 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 6AC80287B7 for ; Fri, 28 Jun 2019 20:08:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727074AbfF1UIA (ORCPT ); Fri, 28 Jun 2019 16:08:00 -0400 Received: from mail-pf1-f193.google.com ([209.85.210.193]:41575 "EHLO mail-pf1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726809AbfF1UIA (ORCPT ); Fri, 28 Jun 2019 16:08:00 -0400 Received: by mail-pf1-f193.google.com with SMTP id m30so3515572pff.8 for ; Fri, 28 Jun 2019 13:08:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Ek8qE1fiI2toyR6h4GSeKfgpYT40/3E34bwIIlJLMOg=; b=ecWeQ8OYbdfLgWfyfqB4lbidfwi0yGSgMyaqjgavf3cROyrE+F2+bMg9ihal5HK1h5 3ewokUj1zwKjbqnf88NL2BdZyt5XeOYwO3qyDqXUrmDaXPKj7n8kSRlaejolN6dBYQ+l PxF6suodRDBLEMWjhhiuPyk16wjynmDgbBBXNazp7ngWK3edI9WVL/r2ZmS5rRl9GKVi A2IObBj+/byDOZr9t4o4e6O3BgvMsG7q9jgjxgygX5Y26uxHO/47XiN1L9Q2O+b5Avi9 NC3Y7UgCA38xdfMsrodADtI/iBXAyABNbewMc/3FbPYNL7D5LsK5fPlD2vMBXMNuXi5z LkRA== X-Gm-Message-State: APjAAAXXgtThYxLr9+vKH/EIaUi9agufgzk0/LSfR8wLd781NG1GZwxi FfwXN11bW5LbbE0yZXwdWW2esJ9HGxI= X-Google-Smtp-Source: APXvYqwvj5PTsqyqvpes6Rwjurzi+eJep2spD22+QffYUj0pDXJ4sJfbkvPhBVSest1i/mW37jY3nQ== X-Received: by 2002:a17:90a:a00d:: with SMTP id q13mr15165007pjp.80.1561752479735; Fri, 28 Jun 2019 13:07:59 -0700 (PDT) Received: from desktop-bart.svl.corp.google.com ([2620:15c:2cd:202:4308:52a3:24b6:2c60]) by smtp.gmail.com with ESMTPSA id 65sm1186010pff.148.2019.06.28.13.07.58 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 28 Jun 2019 13:07:58 -0700 (PDT) From: Bart Van Assche To: Jens Axboe Cc: linux-block@vger.kernel.org, Christoph Hellwig , Bart Van Assche Subject: [PATCH 4/4] block, documentation: Document discard_zeroes_data, fua, max_discard_segments and write_zeroes_max_bytes Date: Fri, 28 Jun 2019 13:07:45 -0700 Message-Id: <20190628200745.206110-5-bvanassche@acm.org> X-Mailer: git-send-email 2.22.0.410.gd8fdbe21b5-goog In-Reply-To: <20190628200745.206110-1-bvanassche@acm.org> References: <20190628200745.206110-1-bvanassche@acm.org> MIME-Version: 1.0 Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Signed-off-by: Bart Van Assche Reviewed-by: Martin K. Petersen --- Documentation/block/queue-sysfs.txt | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Documentation/block/queue-sysfs.txt b/Documentation/block/queue-sysfs.txt index 1515dcf3dec4..b40b5b7cebd9 100644 --- a/Documentation/block/queue-sysfs.txt +++ b/Documentation/block/queue-sysfs.txt @@ -52,6 +52,16 @@ large discards are issued, setting this value lower will make Linux issue smaller discards and potentially help reduce latencies induced by large discard operations. +discard_zeroes_data (RO) +------------------------ +Obsolete. Always zero. + +fua (RO) +-------- +Whether or not the block driver supports the FUA flag for write requests. +FUA stands for Force Unit Access. If the FUA flag is set that means that +write requests must bypass the volatile cache of the storage device. + hw_sector_size (RO) ------------------- This is the hardware sector size of the device, in bytes. @@ -92,6 +102,10 @@ logical_block_size (RO) ----------------------- This is the logical block size of the device, in bytes. +max_discard_segments (RO) +------------------------- +The maximum number of DMA scatter/gather entries in a discard request. + max_hw_sectors_kb (RO) ---------------------- This is the maximum number of kilobytes supported in a single data transfer. @@ -218,6 +232,12 @@ blk-throttle makes decision based on the samplings. Lower time means cgroups have more smooth throughput, but higher CPU overhead. This exists only when CONFIG_BLK_DEV_THROTTLING_LOW is enabled. +write_zeroes_max_bytes (RO) +--------------------------- +For block drivers that support REQ_OP_WRITE_ZEROES, the maximum number of +bytes that can be zeroed at once. The value 0 means that REQ_OP_WRITE_ZEROES +is not supported. + zoned (RO) ---------- This indicates if the device is a zoned block device and the zone model of the