From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nitin Gupta <ngupta@vflare.org>,
Jerome Marchand <jmarchan@redhat.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Matthew Wilcox <matthew.r.wilcox@intel.com>,
Karam Lee <karam.lee@lge.com>, Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH] zram: rely on the bi_end_io for zram_rw_page fails
Date: Thu, 20 Nov 2014 08:32:32 +0900 [thread overview]
Message-ID: <20141119233232.GA2627@bbox> (raw)
In-Reply-To: <20141119131535.7d848c148535c076a17b9d29@linux-foundation.org>
Hello,
On Wed, Nov 19, 2014 at 01:15:35PM -0800, Andrew Morton wrote:
> On Wed, 19 Nov 2014 08:52:01 +0900 Minchan Kim <minchan@kernel.org> wrote:
>
> > > >
> > > > - /*
> > > > - * Return 0 prevents I/O fallback trial caused by rw_page fail
> > > > - * and upper layer can handle this IO error via page error.
> > > > - */
> > > > + page_endio(page, rw, 0);
> > > > return 0;
> > >
> > > Losing the comment makes me sad. The code is somewhat odd-looking. We
> > > should add some words explaining why we're not reporting errors at this
> > > point.
> >
> > Okay. How about this?
> >
> >
> > diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> > index decca6f161b8..1d7c90d5e0d0 100644
> > --- a/drivers/block/zram/zram_drv.c
> > +++ b/drivers/block/zram/zram_drv.c
> > @@ -975,6 +975,12 @@ static int zram_rw_page(struct block_device *bdev, sector_t sector,
> > err = zram_bvec_rw(zram, &bv, index, offset, rw);
> > out_unlock:
> > up_read(&zram->init_lock);
> > + /*
> > + * If I/O fails, just return error without calling page_endio.
> > + * It causes resubmit the I/O with bio request by rw_page fallback
> > + * and bio I/O complete handler does things to handle the error
> > + * (e.g., set_page_dirty of swap_writepage fail).
> > + */
> > if (err == 0)
> > page_endio(page, rw, 0);
> > return err;
>
> I don't understand the comment :( bdev_read_page() doesn't resubmit the
> IO if block_device_operations.rw_page() returns zero and it's unclear
It's not bdev_read_page but upper functions.
(ie, do_mpage_readpage, swap_readpage, __mpage_writepage, __swap_writepage)
> how the bio I/O complete handler (which one?) gets involved.
bio->bi_end_io.
>
> It would help in the comment was more specific. Instead of using vague
> terms like "rw_page fallback" and "bio I/O complete handler", use
> actual function names so the reader understand exactly what code we're
> referring to.
Indeed. I was terrible.
Hope this is better.
prev parent reply other threads:[~2014-11-19 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 0:49 [PATCH] zram: rely on the bi_end_io for zram_rw_page fails Minchan Kim
2014-11-15 9:19 ` Sergey Senozhatsky
2014-11-18 23:23 ` Andrew Morton
2014-11-18 23:52 ` Minchan Kim
2014-11-19 21:15 ` Andrew Morton
2014-11-19 23:32 ` Minchan Kim [this message]
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=20141119233232.GA2627@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=jmarchan@redhat.com \
--cc=karam.lee@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky@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;
as well as URLs for NNTP newsgroup(s).