From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
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: 26 Jul 2002 11:56:04 +0100 [thread overview]
Message-ID: <1027680964.13428.37.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <12015.1027676388@redhat.com>
On Fri, 2002-07-26 at 10:39, David Woodhouse wrote:
>
> alan@lxorguk.ukuu.org.uk said:
> > It doesn't work with an MMU either. Consider O_DIRECT file writing
> > from such a page
>
> Hmmm.
>
> O_DIRECT writing of data from an XIP-mapped page to a file on the same chip
> ain't ever going to work. Writing to something elsewhere should be fine --
> if a page is locked when the chip driver wants to go talk to the chip, the
> chip driver has to wait for that page to become unlocked. No?
Now consider two events each locking the page the other wishes to write
to. At that point you may want to stop digging any deeper holes
next prev parent reply other threads:[~2002-07-26 9:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 6:56 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 9:39 ` David Woodhouse
2002-07-26 9:58 ` David Woodhouse
2002-07-26 14:03 ` David Woodhouse
2002-07-26 16:01 ` David Woodhouse
2002-07-26 16:27 ` David Woodhouse
2002-07-26 17:27 ` Alan Cox
2002-07-26 17:11 ` Alan Cox
2002-07-26 14:50 ` Alan Cox
2002-07-26 10:56 ` Alan Cox [this message]
2002-07-26 10:39 ` Alan Cox
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=1027680964.13428.37.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davidm@snapgear.com \
--cc=dwmw2@infradead.org \
--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
all inboxes | Powered by JetHome®