From: Chris Mason <clm@fb.com>
To: Maxim Patlasov <mpatlasov@virtuozzo.com>, <dsterba@suse.cz>
Cc: <jbacik@fb.com>, <linux-kernel@vger.kernel.org>,
<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: limit async_work allocation and worker func duration
Date: Tue, 13 Dec 2016 14:03:31 -0500 [thread overview]
Message-ID: <47667065-cf42-50b7-2862-d270628dc8f8@fb.com> (raw)
In-Reply-To: <2d4aaf16-b9b3-6cd9-d542-c74f00811c93@virtuozzo.com>
On 12/12/2016 03:35 PM, Maxim Patlasov wrote:
> On 12/12/2016 06:54 AM, David Sterba wrote:
>
> As far as we don't have any NO_THRESHOLD users of
> btrfs_workqueue_normal_congested for now, I tend to think it's better to
> add a descriptive comment and simply return "false" from
> btrfs_workqueue_normal_congested rather than trying to address some
> future needs now. See please v2 of the patch.
>
Thanks, I've got v2 and added a cc for stable to v3.15+, which isn't
exactly right, but its when the new workqueue system was put in place.
-chris
prev parent reply other threads:[~2016-12-13 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 1:51 [PATCH] btrfs: limit async_work allocation and worker func duration Maxim Patlasov
2016-12-12 14:54 ` David Sterba
2016-12-12 16:33 ` Holger Hoffstätte
2016-12-12 20:35 ` Maxim Patlasov
2016-12-13 19:03 ` Chris Mason [this message]
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=47667065-cf42-50b7-2862-d270628dc8f8@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatlasov@virtuozzo.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).