From: "Sekhar Nori" <nori.sekhar@gmail.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Priority inversion when using MTD
Date: Thu, 17 May 2007 22:06:28 +0530 [thread overview]
Message-ID: <93840d070705170936o7188807do17f29422f7e31404@mail.gmail.com> (raw)
In-Reply-To: <1179409930.2859.495.camel@shinybook.infradead.org>
On 5/17/07, David Woodhouse <dwmw2@infradead.org> wrote:
> On Thu, 2007-05-17 at 18:50 +0530, Sekhar Nori wrote:
> > I have a high priority SCHED_FIFO task which runs out of a squashfs file system.
> > When this process needs to fetch a page from the flash (due to demand paging),
> > it is sometimes made to wait for another low priority SCHED_NORMAL
> > task which is doing an erase on some other mtd partition.
> ...
> > Is there any way to avoid this scenario? Any help/pointers would be appreciated.
>
> mlockall(2)
But doing so for all SCHED_FIFO tasks would make the system run out of memory :(
-
Sekhar Nori
prev parent reply other threads:[~2007-05-17 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 13:20 Priority inversion when using MTD Sekhar Nori
2007-05-17 13:52 ` David Woodhouse
2007-05-17 16:36 ` Sekhar Nori [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=93840d070705170936o7188807do17f29422f7e31404@mail.gmail.com \
--to=nori.sekhar@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox