Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: David Oberhollenzer <david.oberhollenzer@sigma-star.at>,
	Kees Trommel <ctrommel@aimvalley.nl>,
	linux-mtd@lists.infradead.org
Subject: Re: Add --skip-all-ffs option to mtd-utils nandwrite
Date: Wed, 7 Dec 2016 17:07:00 +0100	[thread overview]
Message-ID: <20161207170700.4b967faa@bbrezillon> (raw)
In-Reply-To: <d4a1082b-d79a-8c90-b17d-5d559e32308a@gmail.com>

On Wed, 7 Dec 2016 15:09:49 +0100
Marek Vasut <marek.vasut@gmail.com> wrote:

> On 12/07/2016 09:21 AM, David Oberhollenzer wrote:
> > On 12/07/2016 06:01 AM, Marek Vasut wrote:  
> >> +               if (skipallffs)
> >> +               {
> >> +                       for (ii = 0; ii < mtd.min_io_size; ii +=
> >> sizeof(uint32_t))
> >> +                       {
> >> +                               if (*(uint32_t*)(writebuf + ii) !=
> >> 0xffffffff)
> >> +                                       break;
> >>
> >> Is this memcmp()-alike function ?
> >>
> >> +                       }
> >> +                       if (ii == mtd.min_io_size)
> >> +                               allffs = 1;
> >> +               }
> >> +               if (!allffs) {  
> > The point of the patch is not to write a page that is filled with 0xFF bytes.
> > A feature that is turned off by default and can be activated via a command
> > line switch.  
> 
> That much I figured out
> 
> > The code you are trying to replace tries to figure out if an entire block of
> > memory is set to 0xFF. The code path should be conditional, as this feature
> > is turned off unless explicitly requested.  
> 
> And to do that, we need to open-code it like above ?
> Looks pretty crappy.

I agree with Marek on one point: we're likely to need the 0xff-pattern
check in other places, so how about implementing a helper (or several
helpers) in libmtd?

> 
> >> This could be simply turned to:
> >>
> >> ret = 0;
> >> if (!memcmp(writebuf, writebuf + 1, mtd.min_io_size - 1)) {
> >>     ret = mtd_write(....);
> >> }  

Oh, nice trick! It works with and additional writebuf[0] == 0xff test.
However I'm concerned about readability (can be addressed with a comment
explaining what you're doing), and perfs (memcmp is likely to be
optimized for aligned accesses, and you defeat that with your writebuf
+ 1).

Here's a proposal for the pattern comparison API:

struct pattern_buf {
	unsigned int size;
	void *buf;
}

const struct pattern_buf *mtd_create_pattern_buf(int size, u8 pattern);
void mtd_free_pattern_buf(const struct pattern_buf *pbuf);
bool mtd_check_pattern(const struct pattern_buf *pbuf, void *buf,
		       int size);

This way you can allocate a pattern buffer of pagesize and re-use it for
each new page you want to check. This also solves the unaligned
memcmp() problem.

  reply	other threads:[~2016-12-07 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 16:14 Add --skip-all-ffs option to mtd-utils nandwrite Kees Trommel
2016-12-05 19:13 ` David Oberhollenzer
2016-12-06  8:29   ` Kees Trommel
2016-12-06 13:19     ` David Oberhollenzer
2016-12-07  5:01       ` Marek Vasut
2016-12-07  8:21         ` David Oberhollenzer
2016-12-07 14:09           ` Marek Vasut
2016-12-07 16:07             ` Boris Brezillon [this message]
2016-12-07 16:31               ` Marek Vasut
2016-12-07 16:59                 ` Boris Brezillon
2016-12-08  4:14                   ` Marek Vasut

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=20161207170700.4b967faa@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=ctrommel@aimvalley.nl \
    --cc=david.oberhollenzer@sigma-star.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    /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