From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Haws <jhaws@sdl.usu.edu>
Cc: "bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"mingo@kernel.org" <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"deepa.kernel@gmail.com" <deepa.kernel@gmail.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>
Subject: Re: [RFC][PATCH] ipc: mqueue: wq_add priority changed to dynamic priority
Date: Mon, 11 Dec 2017 15:15:37 -0500 [thread overview]
Message-ID: <20171211151537.58212890@gandalf.local.home> (raw)
In-Reply-To: <1513022070.2797.13.camel@sdl.usu.edu>
On Mon, 11 Dec 2017 19:54:33 +0000
Jonathan Haws <jhaws@sdl.usu.edu> wrote:
> > Probably a better subject would be:
> >
> > ipc: mqueue: Have RT tasks queue in by priority in wq_add()
>
> Is the best way to change that just to change it in the email thread or
> resubmit the patch as v2?
That, or whoever takes it could change it before they pull it into git.
>
> >
> > Other than that (and that this doesn't handle DL tasks),
> >
> > Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> >
> > -- Steve
> >
>
> I'm still new to kernel scheduling details - can you elaborate on what
> a DL task is? I'm happy to update the patch to handle DL tasks as well
> if it makes sense to do so.
DL is a SCHED_DEADLINE task that has a dynamic priority that changes
over time. It's not a trivial task to compare them in these situations,
and they are currently not used much, and having DL tasks use this
queue is probably even more rare of an occurrence.
-- Steve
prev parent reply other threads:[~2017-12-11 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1513006652-7014-1-git-send-email-jhaws@sdl.usu.edu>
2017-12-11 17:12 ` [RFC][PATCH] ipc: mqueue: wq_add priority changed to dynamic priority Jonathan Haws
2017-12-11 19:32 ` Steven Rostedt
2017-12-11 19:54 ` Jonathan Haws
2017-12-11 20:15 ` Steven Rostedt [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=20171211151537.58212890@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=deepa.kernel@gmail.com \
--cc=jhaws@sdl.usu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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