All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
	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: Tue, 28 Jun 2016 10:49:49 -0700	[thread overview]
Message-ID: <20160628174949.GC80724@google.com> (raw)
In-Reply-To: <20160628140500.GN20657@pengutronix.de>

On Tue, Jun 28, 2016 at 04:05:00PM +0200, Sascha Hauer wrote:
> On Tue, Jun 28, 2016 at 04:00:29PM +0300, Artem Bityutskiy wrote:
> > If the VID header is in the first subpage, the MTD level probably needs
> > to read the entire subpage anyway, because of per-subpage ECC. This is
> > why we give it a buffer of subpage size.
> 
> The gpmi NAND driver allows reading subpages (NAND_SUBPAGE_READ is set), but
> it does not allow writing subpages (NAND_NO_SUBPAGE_WRITE is also set).
> With this mtd->subpage_sft becomes 0 and ubi->hdrs_min_io_size becomes
> the full page size.
> UBI does not distinguish between the minimum read size and the minimum
> write size. We could pass this information from mtd to UBI, then UBI
> could make use of it.

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.

Brian

  parent reply	other threads:[~2016-06-28 17:50 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 [this message]
2016-06-29  3:51       ` Artem Bityutskiy
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=20160628174949.GC80724@google.com \
    --to=computersforpeace@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=dedekind1@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.