From: "Jörn Engel" <joern@logfs.org>
To: Alexey Korolev <akorolev@infradead.org>
Cc: linux-mtd@lists.infradead.org, tglx@linutronix.de,
dwmw2@infradead.org, vasiliy.leonenko@gmail.com
Subject: Re: [RFC/PATCH 2/3] NAND multiple plane feature
Date: Fri, 6 Jun 2008 18:22:39 +0200 [thread overview]
Message-ID: <20080606162238.GA30407@logfs.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0806061448270.26291@pentafluge.infradead.org>
On Fri, 6 June 2008 15:01:05 +0100, Alexey Korolev wrote:
>
> We just tried to check your scenario. It is not
> possible to overwrite something if JFFS2 returned -ENOSPC until
> something got deleted.
>
> In fact our test suite do not include this test case. We have another.
> Write file1 at about 5% of whole space, write file2 for rest of space.
> Delete file1. Do step 2.
> In this not so good case we got the following numbers:
>
> single-plane:
> 73 sec 424541 usec
>
> dual-plane:
> 69 sec 428637 usec
An improvement instead of the expected regression. Impressive.
Jörn
--
tglx1 thinks that joern should get a (TM) for "Thinking Is Hard"
-- Thomas Gleixner
next prev parent reply other threads:[~2008-06-06 16:22 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
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 [this message]
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=20080606162238.GA30407@logfs.org \
--to=joern@logfs.org \
--cc=akorolev@infradead.org \
--cc=dwmw2@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.