All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Rik van Riel <riel@redhat.com>, axboe@kernel.org
Cc: fweisbec@redhat.com, mingo@kernel.org,
	linux-kernel@vger.kernel.org, lcapitulino@redhat.com,
	mtosatti@redhat.com
Subject: Re: [PATCH RFC] nohz,blk-mq: do not create blk-mq workqueues on nohz dedicated CPUs
Date: Tue, 31 Mar 2015 09:07:11 -0600	[thread overview]
Message-ID: <551AB81F.8020806@kernel.dk> (raw)
In-Reply-To: <20150331102726.076a6860@annuminas.surriel.com>

On 03/31/2015 08:27 AM, Rik van Riel wrote:
> CPUs with nohz_full do not want disruption from timer interrupts,
> or other random system things.  This includes block mq work.
>
> There is another issue with block mq vs. realtime tasks that run
> 100% of the time, which is not uncommon on systems that have CPUs
> dedicated to real time use with isolcpus= and nohz_full=
>
> Specifically, on systems like that, a block work item may never
> get to run, which could lead to filesystems getting stuck forever.
>
> We can avoid both issues by not scheduling blk-mq workqueues on
> cpus in nohz_full mode.
>
> Question for Jens: should we try to spread out the load for
> currently offline and nohz CPUs across the remaining CPUs in
> the system, to get the full benefit of blk-mq in these situations?
>
> If so, do you have any preference on how I should implement that?
>
> Cc: Frederic Weisbecker <fweisbec@redhat.com>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Jens Axboe <axboe@kernel.org>
> Signed-off-by: Rik van Riel <riel@redhat.com>
> ---
>   block/blk-mq.c | 5 +++++
>   1 file changed, 5 insertions(+)
>
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index 4f4bea21052e..1004d6817fa4 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -21,6 +21,7 @@
>   #include <linux/sched/sysctl.h>
>   #include <linux/delay.h>
>   #include <linux/crash_dump.h>
> +#include <linux/tick.h>
>
>   #include <trace/events/block.h>
>
> @@ -1760,6 +1761,10 @@ static void blk_mq_init_cpu_queues(struct request_queue *q,
>   		if (!cpu_online(i))
>   			continue;
>
> +		/* Do not schedule work on nohz full dedicated CPUs. */
> +		if (tick_nohz_full_cpu(i))
> +			continue;

Is this CPU ever going to queue IO? If yes, then it needs to be mapped. 
If userspace never runs on it and submits IO, then we'll never run 
completions on it nor schedule the associated workqueue. So I really 
don't see how it doesn't already work, as-is.

-- 
Jens Axboe


  parent reply	other threads:[~2015-03-31 15:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 14:27 [PATCH RFC] nohz,blk-mq: do not create blk-mq workqueues on nohz dedicated CPUs Rik van Riel
2015-03-31 15:02 ` Frederic Weisbecker
2015-03-31 23:18   ` Marcelo Tosatti
2015-04-07 13:14     ` Luiz Capitulino
2015-03-31 15:07 ` Jens Axboe [this message]
2015-03-31 15:33   ` Frederic Weisbecker
2015-03-31 15:43     ` Jens Axboe
2015-04-01 16:12       ` Rik van Riel
2015-04-03  1:15         ` Jens Axboe
2015-03-31 23:17 ` Marcelo Tosatti
2015-04-01 14:36   ` Jens Axboe
2015-04-01 14:45     ` Rik van Riel
2015-04-01 14:46       ` Jens Axboe
2015-04-05  5:31 ` Mike Galbraith

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=551AB81F.8020806@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=axboe@kernel.org \
    --cc=fweisbec@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.