From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: cleanup btrfs_async_submit_limit to return the final limit value
Date: Thu, 2 Nov 2017 13:55:15 +0800 [thread overview]
Message-ID: <e9b338ee-853c-7666-6492-8486402a7243@oracle.com> (raw)
In-Reply-To: <134be249-616f-1865-585b-7b66427320c1@suse.com>
On 10/31/2017 10:18 PM, Nikolay Borisov wrote:
>
>
> On 31.10.2017 14:59, Anand Jain wrote:
>> btrfs_async_submit_limit() would return the q depth to be 256, however
>> when we are using it we are making it 2/3 times of it. So instead let
>> the function return the final computed value.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>
> Could you put a bit info about what exactly is this limit controlling in
> the changelog.
Ok will update.
>> ---
>> fs/btrfs/disk-io.c | 6 ++++--
>> fs/btrfs/volumes.c | 1 -
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
>> index dfdab849037b..e58bbc2a68a5 100644
>> --- a/fs/btrfs/disk-io.c
>> +++ b/fs/btrfs/disk-io.c
>> @@ -861,7 +861,10 @@ unsigned long btrfs_async_submit_limit(struct btrfs_fs_info *info)
>> unsigned long limit = min_t(unsigned long,
>> info->thread_pool_size,
>> info->fs_devices->open_devices);
>> - return 256 * limit;
>> + /*
>> + * As of now limit is computed as 2/3 * 256.
>> + */
>
> Drop the "As of now" part, since it doesn't bring any value.
Ok.
Thanks
Anand
>> + return 170 * limit;
>> }
>>
>> static void run_one_async_start(struct btrfs_work *work)
>> @@ -887,7 +890,6 @@ static void run_one_async_done(struct btrfs_work *work)
>> fs_info = async->fs_info;
>>
>> limit = btrfs_async_submit_limit(fs_info);
>> - limit = limit * 2 / 3;
>>
>> /*
>> * atomic_dec_return implies a barrier for waitqueue_active
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index d1d8aa226bff..8044790c5de6 100644
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -382,7 +382,6 @@ static noinline void run_scheduled_bios(struct btrfs_device *device)
>>
>> bdi = device->bdev->bd_bdi;
>> limit = btrfs_async_submit_limit(fs_info);
>> - limit = limit * 2 / 3;
>>
>> loop:
>> spin_lock(&device->io_lock);
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-11-02 5:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:59 [PATCH] btrfs: cleanup btrfs_async_submit_limit to return the final limit value Anand Jain
2017-10-31 14:18 ` Nikolay Borisov
2017-11-02 5:55 ` Anand Jain [this message]
2017-11-02 6:03 ` [PATCH v2] " Anand Jain
2017-11-06 15:34 ` David Sterba
2017-11-06 15:38 ` David Sterba
2017-11-07 2:22 ` Anand Jain
2017-11-07 2:17 ` [PATCH v3] " Anand Jain
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=e9b338ee-853c-7666-6492-8486402a7243@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).