public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Carsten Otte <cotte@de.ibm.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: carsteno@de.ibm.com, dhowells <dhowells@redhat.com>,
	David Woodhouse <dwmw2@infradead.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH][MTD] mtdpart.c: allow other drivers to get physical address of partition
Date: Fri, 03 Aug 2007 14:21:54 +0200	[thread overview]
Message-ID: <46B31DE2.3050804@de.ibm.com> (raw)
In-Reply-To: <20070803113134.GA19049@lazybastard.org>

Jörn Engel wrote:
> On Fri, 3 August 2007 13:03:49 +0200, Carsten Otte wrote:
>> I see. Trouble for "real time" applications ;-). But once we're 
>> receiving a lot of page faults we end up suspending the erase forever. 
>> We need a deterministic end of the erase cycle as well, don't we?
> Absolutely.
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.

  reply	other threads:[~2007-08-03 12:22 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 [this message]
2007-08-03 12:58                         ` Jörn Engel
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=46B31DE2.3050804@de.ibm.com \
    --to=cotte@de.ibm.com \
    --cc=carsteno@de.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=joern@logfs.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