All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Pringlemeir <bpringlemeir@nbsps.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mtd: vf610_nfc: remove caching of page in buffer
Date: Tue, 07 Apr 2015 10:24:45 -0400	[thread overview]
Message-ID: <87384ckocy.fsf@nbsps.com> (raw)
In-Reply-To: <737e1411311405071d54d0cc5329e5cd@agner.ch> (Stefan Agner's message of "Tue, 07 Apr 2015 15:14:35 +0200")

On  7 Apr 2015, stefan at agner.ch wrote:
> On 2015-04-02 22:30, Bill Pringlemeir wrote:
>> On  2 Apr 2015, stefan at agner.ch wrote:

>> [snip]

>> I also measured 'write performance' with the mtd_speedtest
>> (performing similar patch to the Linux driver) and I see no
>> difference.  I think a write benchmark is more appropriate to test
>> this functionality?  While at least it seems that neither read nor
>> write is affected by the simplification.

> On U-Boot, I just benchmarked the overall boot time since this is most
> important for us. I plan to (re-)integrate the changes into the Linux
> driver and check the performance again later this week.

> Thanks for for the write test. So I can take this as a Ack?

Of course, if you want it,

Acked-by: Bill Pringlemeir <bpringlemeir@nbsps.com>

The OOB patch also significantly decreases UbiFS mounting time in Linux.
I load Linux itself via tftp/network and not using u-boot with nand.  I
guess I should try that.

> I will send all the NFC changes in one patchset as v2 probably later
> today.

  reply	other threads:[~2015-04-07 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02  9:05 [U-Boot] [PATCH 1/2] mtd: vf610_nfc: remove caching of page in buffer Stefan Agner
2015-04-02  9:05 ` [U-Boot] [PATCH 2/2] mtd: vf610_nfc: implement OOB only read Stefan Agner
2015-04-02 20:30 ` [U-Boot] [PATCH 1/2] mtd: vf610_nfc: remove caching of page in buffer Bill Pringlemeir
2015-04-07 13:14   ` Stefan Agner
2015-04-07 14:24     ` Bill Pringlemeir [this message]
2015-04-07 15:09       ` Stefan Agner
2015-04-07 16:48         ` Bill Pringlemeir

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=87384ckocy.fsf@nbsps.com \
    --to=bpringlemeir@nbsps.com \
    --cc=u-boot@lists.denx.de \
    /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.