From: Oliver Neukum <oneukum@suse.de>
To: jimmie.davis@l-3com.com
Cc: umgwanakikbuti@gmail.com, 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: Fri, 21 Mar 2014 14:35:25 +0100 [thread overview]
Message-ID: <1395408925.9455.3.camel@linux-fkkt.site> (raw)
In-Reply-To: <FFF95760268D324AB6DD9426E83C8DF70B2E5870@ARLEXCHMBX01.lst.link.l-3com.com>
On Fri, 2014-03-21 at 12:18 +0000, jimmie.davis@l-3com.com wrote:
>
> >How is that different from any other time a task has to yield the CPU
> >for a bit? While your high priority task is blocked for whatever
> >reason, a lower priority task gets to use the CPU.
>
>
> As the submitter of the bug, let me give you my perspective. SCHED_FIFO means run my task until it blocks or a higher priority task pre-empts it. Period.
>
> mlock() doesn't block. check the man page.
It guarantees that all pages be in RAM. That means it has to read them
in if they aren't. How could it do that without blocking?
Regards
Oliver
next prev parent reply other threads:[~2014-03-21 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 20:02 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 [this message]
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
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=1395408925.9455.3.camel@linux-fkkt.site \
--to=oneukum@suse.de \
--cc=artem_fetishev@epam.com \
--cc=jimmie.davis@l-3com.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=umgwanakikbuti@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome