From: David Woodhouse <dwmw2@infradead.org>
To: Kevin Jacobs <jacobs@penguin.theopalgroup.com>
Cc: mtd@infradead.org
Subject: Re: Oh, the many joys of MTD...
Date: Thu, 08 Mar 2001 14:43:00 +0000 [thread overview]
Message-ID: <12369.984062580@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0103080809310.7682-100000@penguin.theopalgroup.com>
jacobs@penguin.theopalgroup.com said:
> My first questions is likely something fairly basic. I've read over
> much of the MTD source and it seems that many of the erase and write
> functions do not deal with concurrent access and CPU cache issues.
> What happens when a {read,write,erase} request comes in for a sector
> that is being {written,erased}?
See the state machine in cfi_cmdset_000[12].c. We wait until the operation
which is currently in progress has completed. Theoretical support for
interruption of erases and writes is there, but it's not yet implemented.
> Also, is it assumed that the memory mapped for MTD devices will not be
> cached by the CPU? If so, is it feasible to add support. If not,
> where is code to flush/update the cache after a write or erase
> operation?
It's assumed that it won't be cached, you are correct.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-03-08 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 13:38 Oh, the many joys of MTD Kevin Jacobs
2001-03-08 14:43 ` David Woodhouse [this message]
2001-03-08 14:49 ` Kevin Jacobs
2001-03-08 16:27 ` Nicolas Pitre
2001-03-08 16:29 ` Kevin Jacobs
2001-03-08 17:41 ` Vipin Malik
2001-03-08 17:40 ` Kevin Jacobs
2001-03-09 2:54 ` Alice Hennessy
2001-03-12 10:10 ` Robert Kaiser
-- strict thread matches above, loose matches on Subject: below --
2001-03-13 7:24 Jonas Holmberg
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=12369.984062580@redhat.com \
--to=dwmw2@infradead.org \
--cc=jacobs@penguin.theopalgroup.com \
--cc=mtd@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