From: Peter Zijlstra <peterz@infradead.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Corey Minyard <cminyard@mvista.com>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: [RT PATCH 2/2] block: blk-mq: move blk_queue_usage_counter_release() into process context
Date: Tue, 13 Mar 2018 21:10:39 +0100 [thread overview]
Message-ID: <20180313201039.GB4082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180313184240.ndq2pw2fmvhkwidc@linutronix.de>
On Tue, Mar 13, 2018 at 07:42:41PM +0100, Sebastian Andrzej Siewior wrote:
> +static void blk_queue_usage_counter_release_swork(struct swork_event *sev)
> +{
> + struct request_queue *q =
> + container_of(sev, struct request_queue, mq_pcpu_wake);
> +
> + wake_up_all(&q->mq_freeze_wq);
> +}
> +
> static void blk_queue_usage_counter_release(struct percpu_ref *ref)
> {
> struct request_queue *q =
> container_of(ref, struct request_queue, q_usage_counter);
>
> - wake_up_all(&q->mq_freeze_wq);
> + swork_queue(&q->mq_pcpu_wake);
> }
Depending on if we expect there to actually be wakeups, you could do
something like:
if (wq_has_sleepers(&q->mq_freeze_wq))
swork_queue(&q->mq_pcpu_wake));
avoiding the whole workqueue thing in the case there wasn't anybody
waiting for it. But since I don't know this code, I can't say if it
makes sense or not. Tejun?
next prev parent reply other threads:[~2018-03-13 20:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 15:08 Warning from swake_up_all in 4.14.15-rt13 non-RT Corey Minyard
2018-03-06 17:46 ` Sebastian Andrzej Siewior
2018-03-06 22:51 ` Corey Minyard
2018-03-07 15:45 ` Corey Minyard
2018-03-08 17:41 ` Sebastian Andrzej Siewior
2018-03-08 19:54 ` Corey Minyard
2018-03-09 11:04 ` Sebastian Andrzej Siewior
2018-03-09 13:29 ` Corey Minyard
2018-03-09 14:58 ` Sebastian Andrzej Siewior
2018-03-09 16:03 ` Corey Minyard
2018-03-09 17:46 ` Peter Zijlstra
2018-03-09 20:25 ` Sebastian Andrzej Siewior
2018-03-09 22:26 ` Peter Zijlstra
2018-03-12 10:51 ` Sebastian Andrzej Siewior
2018-03-12 13:27 ` Peter Zijlstra
2018-03-12 14:11 ` Sebastian Andrzej Siewior
2018-03-12 14:29 ` Peter Zijlstra
2018-03-12 19:51 ` Sebastian Andrzej Siewior
2018-03-13 18:40 ` [RT PATCH 1/2] Revert "block: blk-mq: Use swait" Sebastian Andrzej Siewior
2018-03-13 18:42 ` [RT PATCH 2/2] block: blk-mq: move blk_queue_usage_counter_release() into process context Sebastian Andrzej Siewior
2018-03-13 20:10 ` Peter Zijlstra [this message]
2018-03-14 15:23 ` Sebastian Andrzej Siewior
2018-03-09 22:02 ` Warning from swake_up_all in 4.14.15-rt13 non-RT Corey Minyard
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=20180313201039.GB4082@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@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
all inboxes | Powered by JetHome®