From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Ungerer <gerg@snapgear.com>,
linux-kernel@vger.kernel.org,
David McCullough <davidm@snapgear.com>
Subject: Re: [PATCH]: uClinux (MMU-less) patches against 2.5.28
Date: Fri, 26 Jul 2002 15:03:25 +0100 [thread overview]
Message-ID: <26333.1027692205@redhat.com> (raw)
In-Reply-To: <1027695029.13428.45.camel@irongate.swansea.linux.org.uk>
alan@lxorguk.ukuu.org.uk said:
> Anything where you rely on locking the pages and can get a loop of
> locked/absent pages and deadlock
Good point -- so if a writer encounters a locked page when it's trying to
unmap them all, it needs to still allow other pages to be mapped in while
it waits for the original page to become unlocked. That avoids the deadlock
-- but leaves us with the potential for livelock, with the writer being
starved by too many other things locking down the pages in question.
I suspect the number of pages getting locked will be sufficiently small
that the deadlock does not occur.
In what circumstances will such mmapped pages get locked?
The case of O_DIRECT or rawio writes to flash is easily avoided -- just
don't allow raw or O_DIRECT writes to flash from _anywhere_ while XIP is in
use. O_DIRECT and rawio to other destinations is fine. What else? Assume
we don't permit mlock() :)
--
dwmw2
next prev parent reply other threads:[~2002-07-26 14:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 6:56 [PATCH]: uClinux (MMU-less) patches against 2.5.28 Greg Ungerer
2002-07-25 14:52 ` David Woodhouse
2002-07-26 0:08 ` Greg Ungerer
2002-07-26 1:20 ` Greg Ungerer
2002-07-26 8:19 ` David Woodhouse
2002-07-26 10:39 ` Alan Cox
2002-07-26 9:39 ` David Woodhouse
2002-07-26 10:56 ` Alan Cox
2002-07-26 9:58 ` David Woodhouse
2002-07-26 14:50 ` Alan Cox
2002-07-26 14:03 ` David Woodhouse [this message]
2002-07-26 17:11 ` Alan Cox
2002-07-26 16:01 ` David Woodhouse
2002-07-26 17:27 ` Alan Cox
2002-07-26 16:27 ` David Woodhouse
2002-07-26 15:08 ` gerg
2002-07-26 15:45 ` David Woodhouse
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=26333.1027692205@redhat.com \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidm@snapgear.com \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.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