public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: kmpark@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: [RFC PATCH] [MTD] [OneNAND] Cache Read support
Date: Wed, 01 Aug 2007 11:52:01 +0300	[thread overview]
Message-ID: <46B049B1.3000608@nokia.com> (raw)
In-Reply-To: <001c01c7d40a$e57aa4d0$e1ac580a@swcenter.sec.samsung.co.kr>

ext Kyungmin Park wrote:
>  
>> ext Kyungmin Park wrote:
>>> This patch supports the Cache Read feature in OneNAND.
>>> It's similar with read-while-loading except while read it does sensing the page buffer in NAND
>> core.
>>> So it's called Transfer-While-Sensing. you can find it in OneNAND Spec. in detail.
>>>
>>> Now there's no big performance gain in our test board, Apollon(OMAP2). But others are maybe
>> different.
>>> Any comments are welcome.
>> Cool!
>>
>> Presume you have run the NAND tests
> 
> Sure, it passed NAND tests.
> 
> Could you review the code?

I will try to find some time to look at it maybe this week.

> I wonder why there's no performance gain. It's faster than read-while-loading in the Spec.
> Software overhead? Or there's not many 2 or more pages read?

How are you measuring performance?  I would suggest either dd (if you don't have bad blocks)
or write your own program.

As I see it, unless the read from dataRAM is faster than the sensing/transfer, there won't be
a performance improvement.  So the faster the OneNAND frequency the better.  Ditto bus and
CPU frequencies probably (for memcpy).

      reply	other threads:[~2007-08-01  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  0:20 [RFC PATCH] [MTD] [OneNAND] Cache Read support Kyungmin Park
2007-08-01  6:24 ` Adrian Hunter
2007-08-01  7:09   ` Kyungmin Park
2007-08-01  8:52     ` Adrian Hunter [this message]

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=46B049B1.3000608@nokia.com \
    --to=ext-adrian.hunter@nokia.com \
    --cc=kmpark@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