All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Cc: linux-mtd@lists.infradead.org,
	Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH] ubi: do not re-read the data already read out in retry
Date: Fri, 21 Aug 2015 11:17:56 +0200	[thread overview]
Message-ID: <55D6ECC4.5070503@nod.at> (raw)
In-Reply-To: <1440143981-20826-1-git-send-email-yangds.fnst@cn.fujitsu.com>

Am 21.08.2015 um 09:59 schrieb Dongsheng Yang:
> In ubi_io_read(), we will retry if current reading failed
> to read all data we wanted. But we are doing a full re-do
> in the re-try path. Actually, we can skip the data which
> we have already read out in the last reading.
> 
> Signed-off-by: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
> ---
>  drivers/mtd/ubi/io.c | 19 +++++++++++++------
>  1 file changed, 13 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/mtd/ubi/io.c b/drivers/mtd/ubi/io.c
> index 5bbd1f0..a3ac643 100644
> --- a/drivers/mtd/ubi/io.c
> +++ b/drivers/mtd/ubi/io.c
> @@ -127,7 +127,7 @@ int ubi_io_read(const struct ubi_device *ubi, void *buf, int pnum, int offset,
>  		int len)
>  {
>  	int err, retries = 0;
> -	size_t read;
> +	size_t read, already_read = 0;
>  	loff_t addr;
>  
>  	dbg_io("read %d bytes from PEB %d:%d", len, pnum, offset);
> @@ -165,6 +165,7 @@ int ubi_io_read(const struct ubi_device *ubi, void *buf, int pnum, int offset,
>  	addr = (loff_t)pnum * ubi->peb_size + offset;
>  retry:
>  	err = mtd_read(ubi->mtd, addr, len, &read, buf);
> +	already_read += read;

Hmm, this change makes me nervous.

Brian, does MTD core guarantee that upon an erroneous mtd_read() the number of "read" bytes
in "buf" are valid?

So, my fear is that this change will introduce new regressions (due faulty MTD drivers, etc..)
without a real gain.

Thanks,
//richard

  reply	other threads:[~2015-08-21  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  7:59 [PATCH] ubi: do not re-read the data already read out in retry Dongsheng Yang
2015-08-21  9:17 ` Richard Weinberger [this message]
2015-08-24  1:05   ` Dongsheng Yang
2015-08-24  6:46     ` Richard Weinberger
2015-08-24  7:04       ` Dongsheng Yang
2015-08-24 16:59         ` Brian Norris
2015-08-25  0:34           ` Dongsheng Yang
2015-08-24 16:50     ` Brian Norris

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=55D6ECC4.5070503@nod.at \
    --to=richard@nod.at \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=yangds.fnst@cn.fujitsu.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 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.