From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
Daniel Wagner <daniel.wagner@bmw-carit.de>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
bigeasy@linutronix.de, tglx@linutronix.de,
paulmck@linux.vnet.ibm.com
Subject: Re: [RFC v0 0/3] Simple wait queue support
Date: Fri, 7 Aug 2015 07:29:54 -0400 [thread overview]
Message-ID: <20150807072954.1b086402@grimm.local.home> (raw)
In-Reply-To: <20150807092541.GE16853@twins.programming.kicks-ass.net>
On Fri, 7 Aug 2015 11:25:41 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> > For cwait? That's the complex wait queue (what the current wait queues
> > will be called in the future).
>
> Urgh, I don't think we should go rename that.. that's going to be lots
> of pain for no to little gain.
I thought we decided that we would have the end result be that the
default be the simple wait queue, and those that need more complexity,
would have a complex wait queue, as IIRC, the simple wait queue can
replace the majority of the existing wait queues.
-- Steve
next prev parent reply other threads:[~2015-08-07 11:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 13:30 Daniel Wagner
2015-08-05 13:30 ` [RFC v0 1/3] KVM: use simple waitqueue for vcpu->wq Daniel Wagner
2015-08-05 13:30 ` [RFC v0 2/3] sched/completion: convert completions to use simple wait queues Daniel Wagner
2015-08-05 13:30 ` [RFC v0 3/3] rcu: use simple wait queues where possible in rcutree Daniel Wagner
2015-08-06 19:22 ` [RFC v0 0/3] Simple wait queue support Paul Gortmaker
2015-08-06 19:31 ` Steven Rostedt
2015-08-06 21:36 ` Peter Zijlstra
2015-08-06 22:14 ` Steven Rostedt
2015-08-07 9:25 ` Peter Zijlstra
2015-08-07 11:29 ` Steven Rostedt [this message]
2015-08-07 6:42 ` Daniel Wagner
2015-08-07 12:00 ` Daniel Wagner
2015-08-11 6:24 ` Daniel Wagner
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=20150807072954.1b086402@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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®