From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd@lists.infradead.org,
boris.brezillon@free-electrons.com,
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:49:48 +0300 [thread overview]
Message-ID: <1467172188.2456.64.camel@gmail.com> (raw)
In-Reply-To: <20160628174304.GA80724@google.com>
On Tue, 2016-06-28 at 10:43 -0700, Brian Norris wrote:
> Hi Artem,
>
> I'll comment on the other branches of this thread, but one thing
> here:
>
> On Tue, Jun 28, 2016 at 04:00:29PM +0300, Artem Bityutskiy wrote:
> > Therefore, unless I misunderstood this patch - it introduces a
> > regression to those old setups at least (forces MTD to use an
> > intermediate buffer rather than copy data from NAND directly to the
> > buffer supplied by UBI)
>
> It's really a balance between speed of the flash and speed of the
> memcpy().
Sure.
> I believe Boris may have benchmarked some of this recently,
> but I'm really inclined to believe that reading several times as much
> as
> you need from flash is much worse than doing some extra memcpy().
That's probably true.
> So
> even if we introduce an extra memcpy(), it might still be worth it to
> save the extra wait-for-flash time.
Right.
> Intuitively, I expect that these days, the I/O time is much more
> significant than any memcpy().
All good points. Besides indeed in case of the subpage the memcpy() is
present anyway for (for unexpected reasons).
So yeah, I think the concern I rose is a non-issue and we could proceed
with Sascha's patch. Thanks!
next prev parent reply other threads:[~2016-06-29 3: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
2016-06-29 3:51 ` Artem Bityutskiy
2016-06-28 17:43 ` Brian Norris
2016-06-29 3:49 ` Artem Bityutskiy [this message]
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=1467172188.2456.64.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).