From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: jimmie.davis@l-3com.com
Cc: luto@amacapital.net, oneukum@suse.de, artem_fetishev@epam.com,
peterz@infradead.org, kosaki.motohiro@jp.fujitsu.com,
linux-kernel@vger.kernel.org
Subject: RE: Bug 71331 - mlock yields processor to lower priority process
Date: Thu, 27 Mar 2014 06:35:35 +0100 [thread overview]
Message-ID: <1395898535.5512.72.camel@marge.simpson.net> (raw)
In-Reply-To: <FFF95760268D324AB6DD9426E83C8DF70B2E725C@ARLEXCHMBX01.lst.link.l-3com.com>
On Thu, 2014-03-27 at 04:20 +0000, jimmie.davis@l-3com.com wrote:
> The example code submitted into bugzilla (chase back on the thread a
> bit, there is a reference) shows the problem.
>
> Two threads, TaskA (high priority) and TaskB (low priority). Assigned
> to the same processor, explicitly for the guarantee that only one of
> them can execute at a time.
Your priority based serialization guarantee does not exist. Tasks can
be and are put to sleep. When that happens, a lower priority runnable
task will run. Whether you like that fact or not, it remains a fact.
If you don't want your lower priority task to run, why do you wake it?.
-Mike
>
next prev parent reply other threads:[~2014-03-27 5:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 20:02 Bug 71331 - mlock yields processor to lower priority process Artem Fetishev
2014-03-21 9:23 ` Mike Galbraith
2014-03-21 12:18 ` jimmie.davis
2014-03-21 13:14 ` Mike Galbraith
2014-03-21 14:34 ` jimmie.davis
2014-03-21 14:54 ` Motohiro Kosaki
2014-03-21 13:35 ` Oliver Neukum
2014-03-21 14:01 ` jimmie.davis
2014-03-21 14:41 ` Mike Galbraith
2014-03-21 14:50 ` jimmie.davis
2014-03-27 0:39 ` Andy Lutomirski
2014-03-27 4:20 ` jimmie.davis
2014-03-27 5:35 ` Mike Galbraith [this message]
2014-03-27 6:02 ` Robert Hancock
2014-03-27 11:37 ` jimmie.davis
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=1395898535.5512.72.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=artem_fetishev@epam.com \
--cc=jimmie.davis@l-3com.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oneukum@suse.de \
--cc=peterz@infradead.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 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.