From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] Btrfs: Do not use data_alloc_cluster in ssd mode
Date: Thu, 27 Jul 2017 21:27:56 +0200 [thread overview]
Message-ID: <f8e0ea32-4b6a-778b-10e2-99676160e422@mendix.com> (raw)
In-Reply-To: <pan$12971$566fe832$ff60933c$6921c466@cox.net>
On 07/27/2017 09:11 PM, Duncan wrote:
> Hans van Kranenburg posted on Wed, 26 Jul 2017 21:59:25 +0200 as
> excerpted:
>
>> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
>> index 4f8f75d9e839..b091dd3f5b38 100644
>> --- a/fs/btrfs/ctree.h
>> +++ b/fs/btrfs/ctree.h
>> @@ -472,7 +472,7 @@ struct btrfs_block_rsv {
>> /*
>> * free clusters are used to claim free space in relatively large chunks,
>> * allowing us to do less seeky writes. They are used for all metadata
>> - * allocations and data allocations in ssd mode.
>> + * allocations and data allocations in ssd_spread mode.
>> */
>> struct btrfs_free_cluster {
>> spinlock_t lock;
>
> That (post-patch) comment says all metadata and data allocations in
> ssd_spread mode, but if my understanding is correct, it'll also use
> free clusters for metadata (only, not data, the patch only changing)
> the data behavior) in normal ssd mode.
>
> Perhaps that (metadata only use of free clusers in ssd mode) should be
> mentioned as well, since post-patch there's now a distinction to be made?
The text is confusing yes.
It can be read as...
(all metadata allocations and data allocations) in ssd_spread mode
or...
(all metadata allocations) and (data allocations in ssd_spread mode)
...the second one being correct.
Good catch.
I changed it in: "They are used for all metadata allocations. In
ssd_spread mode they are also used for data allocations."
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-07-27 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 19:59 [PATCH v2] Btrfs: Do not use data_alloc_cluster in ssd mode Hans van Kranenburg
2017-07-26 20:01 ` Hans van Kranenburg
2017-07-27 19:11 ` Duncan
2017-07-27 19:27 ` Hans van Kranenburg [this message]
2017-07-28 6:31 ` [PATCH v3] btrfs: " Hans van Kranenburg
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=f8e0ea32-4b6a-778b-10e2-99676160e422@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox