From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: boris.brezillon@free-electrons.com,
linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH v2] UBI: only read necessary size when reading the VID header
Date: Wed, 29 Jun 2016 06:51:03 +0300 [thread overview]
Message-ID: <1467172263.2456.66.camel@gmail.com> (raw)
In-Reply-To: <20160628174949.GC80724@google.com>
On Tue, 2016-06-28 at 10:49 -0700, Brian Norris wrote:
> In reading Artem's first objection, I was noticing the same thing and
> came to a similar conclusion. I guess we can't really get by with UBI
> just guessing at the ideal read size. Right now, it gets it too large
> most of the time, since often, NAND controllers can support sub-page
> reads, but not sub-page writes (or even if the controller can, the
> flash
> can't -- like all MLC or even many modern SLC), so a single number
> (writesize >> subpage_sf) is not sufficient.
Yes, this is a good opportunity for speed optimizations indeed.
next prev parent reply other threads:[~2016-06-29 3:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 11:51 [PATCH v2] UBI: only read necessary size when reading the VID header Sascha Hauer
2016-06-28 12:05 ` Richard Weinberger
2016-06-28 13:00 ` Artem Bityutskiy
2016-06-28 13:32 ` Richard Weinberger
2016-06-28 14:05 ` Sascha Hauer
2016-06-28 14:54 ` Artem Bityutskiy
2016-06-28 17:46 ` Brian Norris
2016-07-04 13:52 ` Boris Brezillon
2016-06-28 17:49 ` Brian Norris
2016-06-29 3:51 ` Artem Bityutskiy [this message]
2016-06-28 17:43 ` Brian Norris
2016-06-29 3:49 ` Artem Bityutskiy
2016-07-04 9:38 ` Boris Brezillon
2016-07-04 22:24 ` Richard Weinberger
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=1467172263.2456.66.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.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.