From: Jamie Lokier <jamie@shareable.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: dwmw2@infradead.org, tglx@linutronix.de,
linux-mtd@lists.infradead.org,
Alexey Korolev <akorolev@infradead.org>,
vasiliy.leonenko@gmail.com
Subject: Re: [RFC/PATCH 2/3] NAND multiple plane feature
Date: Mon, 2 Jun 2008 12:28:07 +0100 [thread overview]
Message-ID: <20080602112807.GA728@shareable.org> (raw)
In-Reply-To: <20080601174841.GH13094@logfs.org>
Jörn Engel wrote:
> But hoping for manufacturers to get it right rarely works - it certainly
> didn't work in this case. As it seems, we can either program two planes
> in a weird lock-step process or ignore the feature. And the lock-step
> variant isn't useful for much more than doubling/quadrupling the
> erasesize and writesize. With all the disadvantages that brings. :(
Did you see if the dual plane feature at least allows erasing the next
block while writing the current one, so you can do continuous
streaming log writes without big pauses?
-- Jamie
next prev parent reply other threads:[~2008-06-02 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 13:08 [RFC/PATCH 2/3] NAND multiple plane feature Alexey Korolev
2008-06-01 17:48 ` Jörn Engel
2008-06-02 11:28 ` Jamie Lokier [this message]
2008-06-02 11:36 ` Jörn Engel
2008-06-03 16:57 ` Alexey Korolev
2008-06-03 17:20 ` Jörn Engel
2008-06-05 21:09 ` Jörn Engel
2008-06-06 14:01 ` Alexey Korolev
2008-06-06 16:22 ` Jörn Engel
2008-06-03 17:42 ` Jörn Engel
2008-06-05 16:58 ` Alexey Korolev
2008-06-05 18:58 ` Jörn Engel
2008-06-05 19:13 ` Thomas Gleixner
2008-06-06 10:08 ` Alexey Korolev
2008-06-06 12:16 ` Thomas Gleixner
2008-06-06 13:47 ` Alexey Korolev
2008-06-06 14:19 ` Thomas Gleixner
2008-06-06 14:36 ` Alexey Korolev
2008-06-05 20:03 ` Thomas Gleixner
2008-06-10 17:33 ` Alexey Korolev
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=20080602112807.GA728@shareable.org \
--to=jamie@shareable.org \
--cc=akorolev@infradead.org \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
--cc=vasiliy.leonenko@gmail.com \
/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