From: "Jörn Engel" <joern@logfs.org>
To: carsteno@de.ibm.com
Cc: dhowells <dhowells@redhat.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Jörn Engel" <joern@logfs.org>,
"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH][MTD] mtdpart.c: allow other drivers to get physical address of partition
Date: Fri, 3 Aug 2007 14:58:06 +0200 [thread overview]
Message-ID: <20070803125806.GE19344@lazybastard.org> (raw)
In-Reply-To: <46B31DE2.3050804@de.ibm.com>
On Fri, 3 August 2007 14:21:54 +0200, Carsten Otte wrote:
>
> Hmm. At least this does'nt seem like something that the xip
> infrastructure should be concerned with: it will ask for
> get_xip_page() [or get_xip_pfn()], and return temporary references via
> put_xip_page/pfn(). The mtd layer has to decide when to pospone
> get_xip_page() calls and when to ask for references being returned. On
> the other hand, I think we should make sure get_xip_page() targets may
> call schedule() in case the page we ask for is currently unavailable
> while an erase operation is in progress.
Why schedule()? I believe we should not wait but process the fault
immediatly via one of the methods Jared mentioned:
>> If you get a fault it gets routed to the filesystem .fault or
>> something like that. The .fault routine can:
>> (a) suspend the erase
>> (b) copy the page to RAM
>> (c) update the pte to point to RAM
>> (d) resume the erase
>> -or-
>> (a) suspend the erase
>> (b) reenable the pte
>> (c) wait a short time
>> (d) disable pte again
>> (e) resume the erase
The second variant could be a bit hairy. How can one ensure that (c)
only waits a short while and not much longer? So I tend to prefer the
first variant.
Jörn
--
Courage is not the absence of fear, but rather the judgement that
something else is more important than fear.
-- Ambrose Redmoon
next prev parent reply other threads:[~2007-08-03 13:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 0:04 [PATCH][MTD] mtdpart.c: allow other drivers to get physical address of partition Jared Hulbert
2007-07-27 13:48 ` Jörn Engel
2007-07-27 17:05 ` Jared Hulbert
2007-07-27 17:44 ` Jörn Engel
2007-07-27 20:53 ` Jared Hulbert
2007-07-28 11:43 ` Jörn Engel
2007-07-28 21:08 ` Jared Hulbert
2007-07-31 11:55 ` David Woodhouse
2007-07-31 19:55 ` Jared Hulbert
2007-08-01 11:55 ` Jörn Engel
2007-08-03 1:56 ` Jared Hulbert
2007-08-03 3:01 ` Jörn Engel
2007-08-03 5:23 ` Jared Hulbert
2007-08-03 9:21 ` Jörn Engel
2007-08-03 6:42 ` Jared Hulbert
2007-08-03 12:47 ` Jörn Engel
2007-08-03 22:29 ` Jared Hulbert
2007-08-01 12:18 ` Jörn Engel
2007-08-01 12:59 ` Carsten Otte
2007-08-01 20:37 ` Jared Hulbert
2007-08-01 23:31 ` Jörn Engel
2007-08-02 7:53 ` Carsten Otte
2007-08-02 21:55 ` Jared Hulbert
2007-08-03 7:59 ` Carsten Otte
2007-08-03 9:17 ` Jörn Engel
2007-08-03 11:03 ` Carsten Otte
2007-08-03 11:31 ` Jörn Engel
2007-08-03 12:21 ` Carsten Otte
2007-08-03 12:58 ` Jörn Engel [this message]
2007-08-03 13:09 ` David Woodhouse
2007-08-03 13:18 ` Jörn Engel
2007-08-03 19:45 ` Jared Hulbert
2007-08-03 23:02 ` Jörn Engel
2007-08-04 12:33 ` David Woodhouse
2007-08-04 17:47 ` Jared Hulbert
2007-08-06 6:30 ` Carsten Otte
2007-08-03 18:39 ` Jared Hulbert
2007-08-06 6:23 ` Carsten Otte
2007-08-01 18:03 ` Jared Hulbert
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=20070803125806.GE19344@lazybastard.org \
--to=joern@logfs.org \
--cc=carsteno@de.ibm.com \
--cc=dhowells@redhat.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