mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Holmberg <Hans.Holmberg@wdc.com>
To: Carlos Maiolino <cem@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"Darrick J . Wong" <djwong@kernel.org>, hch <hch@lst.de>,
	"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfs: remove duplicate Zoned Filesystems sections in admin-guide
Date: Tue, 22 Apr 2025 12:35:04 +0000	[thread overview]
Message-ID: <7df3bda8-7450-4446-b810-ada1aaa8d5f2@wdc.com> (raw)
In-Reply-To: <dhowchhm6zfb3hir76tmbmunadqobbkmgaa5uardswon2keggy@3bgfjikvj5sf>

On 22/04/2025 14:10, Carlos Maiolino wrote:
> On Tue, Apr 22, 2025 at 11:50:07AM +0000, Hans Holmberg wrote:
>> Remove the duplicated section and while at it, turn spaces into tabs.
>>
>> Signed-off-by: Hans Holmberg <hans.holmberg@wdc.com>
> 
> Sounds good.
> 
> Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
> 
> Hans, I'm adding a Fixes tag before merging if you don't mind me editing the
> patch before applying.
> 
> Fixes: c7b67ddc3c9 ("xfs: document zoned rt specifics in admin-guide")

Thanks!

> 
> 
>> ---
>>
>> This fixes up the warning reported by Stephen Rothwell for linux-next
>>
>>  Documentation/admin-guide/xfs.rst | 29 ++++++++---------------------
>>  1 file changed, 8 insertions(+), 21 deletions(-)
>>
>> diff --git a/Documentation/admin-guide/xfs.rst b/Documentation/admin-guide/xfs.rst
>> index 3e76276bd488..5becb441c3cb 100644
>> --- a/Documentation/admin-guide/xfs.rst
>> +++ b/Documentation/admin-guide/xfs.rst
>> @@ -562,7 +562,7 @@ The interesting knobs for XFS workqueues are as follows:
>>  Zoned Filesystems
>>  =================
>>
>> -For zoned file systems, the following attribute is exposed in:
>> +For zoned file systems, the following attributes are exposed in:
>>
>>    /sys/fs/xfs/<dev>/zoned/
>>
>> @@ -572,23 +572,10 @@ For zoned file systems, the following attribute is exposed in:
>>  	is limited by the capabilities of the backing zoned device, file system
>>  	size and the max_open_zones mount option.
>>
>> -Zoned Filesystems
>> -=================
>> -
>> -For zoned file systems, the following attributes are exposed in:
>> -
>> - /sys/fs/xfs/<dev>/zoned/
>> -
>> - max_open_zones                 (Min:  1  Default:  Varies  Max:  UINTMAX)
>> -        This read-only attribute exposes the maximum number of open zones
>> -        available for data placement. The value is determined at mount time and
>> -        is limited by the capabilities of the backing zoned device, file system
>> -        size and the max_open_zones mount option.
>> -
>> - zonegc_low_space               (Min:  0  Default:  0  Max:  100)
>> -        Define a percentage for how much of the unused space that GC should keep
>> -        available for writing. A high value will reclaim more of the space
>> -        occupied by unused blocks, creating a larger buffer against write
>> -        bursts at the cost of increased write amplification.  Regardless
>> -        of this value, garbage collection will always aim to free a minimum
>> -        amount of blocks to keep max_open_zones open for data placement purposes.
>> +  zonegc_low_space		(Min:  0  Default:  0  Max:  100)
>> +	Define a percentage for how much of the unused space that GC should keep
>> +	available for writing. A high value will reclaim more of the space
>> +	occupied by unused blocks, creating a larger buffer against write
>> +	bursts at the cost of increased write amplification.  Regardless
>> +	of this value, garbage collection will always aim to free a minimum
>> +	amount of blocks to keep max_open_zones open for data placement purposes.
>> --
>> 2.34.1
> 


  reply	other threads:[~2025-04-22 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <_RxmFF7sLGc26Wr0UDPdK5Mxv9AicUnbJ2I5Cji6QZiiHz5pr9uYx7Zk8xOeDutTUsJvS143LlYYxoitgsEEGA==@protonmail.internalid>
2025-04-22 11:50 ` Hans Holmberg
2025-04-22 12:10   ` Carlos Maiolino
2025-04-22 12:35     ` Hans Holmberg [this message]
2025-04-22 13:52   ` hch
2025-04-22 14:09   ` Carlos Maiolino

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=7df3bda8-7450-4446-b810-ada1aaa8d5f2@wdc.com \
    --to=hans.holmberg@wdc.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®