From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Jerome Marchand <jmarchan@redhat.com>,
Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 2/3] zram: do not pass rw argument to __zram_make_request()
Date: Wed, 15 Jan 2014 11:10:51 +0900 [thread overview]
Message-ID: <20140115021051.GH1992@bbox> (raw)
In-Reply-To: <20140114112723.GA2226@swordfish.minsk.epam.com>
Hello Sergey,
On Tue, Jan 14, 2014 at 02:27:23PM +0300, Sergey Senozhatsky wrote:
> Do not pass rw argument down the __zram_make_request() -> zram_bvec_rw()
> chain, decode it in zram_bvec_rw() instead. Besides, this is the place
> where we distinguish READ (+READ AHEAD) and WRITE bio data directions, so
> account zram RW stats here, instead of __zram_make_request(). This also
> allows to account a real number of zram READ/WRITE operations, not just
> requests (single RW request may cause a number of zram RW ops with separate
> locking, compression/decompression, etc).
>
> v2: use bio_rw() instead of bio_data_dir(). noted by Jerome Marchand.
We don't have any special logic for READA so please use bio_data_dir
instead of bio_rw.
And please Ccing Andrew Morton when you send a updated patch.
Thanks.
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> ---
> drivers/block/zram/zram_drv.c | 33 +++++++++++++++------------------
> 1 file changed, 15 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> index c323e05..2a7682c 100644
> --- a/drivers/block/zram/zram_drv.c
> +++ b/drivers/block/zram/zram_drv.c
> @@ -533,14 +533,21 @@ out:
> }
>
> static int zram_bvec_rw(struct zram *zram, struct bio_vec *bvec, u32 index,
> - int offset, struct bio *bio, int rw)
> + int offset, struct bio *bio)
> {
> int ret;
> + int rw = bio_rw(bio);
>
> - if (rw == READ)
> + if (rw == READA)
> + rw = READ;
> +
> + if (rw == READ) {
> + atomic64_inc(&zram->stats.num_reads);
> ret = zram_bvec_read(zram, bvec, index, offset, bio);
> - else
> + } else {
> + atomic64_inc(&zram->stats.num_writes);
> ret = zram_bvec_write(zram, bvec, index, offset);
> + }
>
> return ret;
> }
> @@ -670,22 +677,13 @@ out:
> return ret;
> }
>
> -static void __zram_make_request(struct zram *zram, struct bio *bio, int rw)
> +static void __zram_make_request(struct zram *zram, struct bio *bio)
> {
> int offset;
> u32 index;
> struct bio_vec bvec;
> struct bvec_iter iter;
>
> - switch (rw) {
> - case READ:
> - atomic64_inc(&zram->stats.num_reads);
> - break;
> - case WRITE:
> - atomic64_inc(&zram->stats.num_writes);
> - break;
> - }
> -
> index = bio->bi_iter.bi_sector >> SECTORS_PER_PAGE_SHIFT;
> offset = (bio->bi_iter.bi_sector &
> (SECTORS_PER_PAGE - 1)) << SECTOR_SHIFT;
> @@ -704,16 +702,15 @@ static void __zram_make_request(struct zram *zram, struct bio *bio, int rw)
> bv.bv_len = max_transfer_size;
> bv.bv_offset = bvec.bv_offset;
>
> - if (zram_bvec_rw(zram, &bv, index, offset, bio, rw) < 0)
> + if (zram_bvec_rw(zram, &bv, index, offset, bio) < 0)
> goto out;
>
> bv.bv_len = bvec.bv_len - max_transfer_size;
> bv.bv_offset += max_transfer_size;
> - if (zram_bvec_rw(zram, &bv, index+1, 0, bio, rw) < 0)
> + if (zram_bvec_rw(zram, &bv, index + 1, 0, bio) < 0)
> goto out;
> } else
> - if (zram_bvec_rw(zram, &bvec, index, offset, bio, rw)
> - < 0)
> + if (zram_bvec_rw(zram, &bvec, index, offset, bio) < 0)
> goto out;
>
> update_position(&index, &offset, &bvec);
> @@ -743,7 +740,7 @@ static void zram_make_request(struct request_queue *queue, struct bio *bio)
> goto error;
> }
>
> - __zram_make_request(zram, bio, bio_data_dir(bio));
> + __zram_make_request(zram, bio);
> up_read(&zram->init_lock);
>
> return;
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2014-01-15 2:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 9:37 [PATCH 0/3] zram stats rework and code cleanup Sergey Senozhatsky
2014-01-14 9:37 ` [PATCH 1/3] zram: drop `init_done' struct zram member Sergey Senozhatsky
2014-01-14 11:03 ` Jerome Marchand
2014-01-15 1:52 ` Minchan Kim
2014-01-14 9:37 ` [PATCH 2/3] zram: do not pass rw argument to __zram_make_request() Sergey Senozhatsky
2014-01-14 11:02 ` Jerome Marchand
2014-01-14 11:13 ` Sergey Senozhatsky
2014-01-14 12:27 ` Jerome Marchand
2014-01-14 11:27 ` [PATCHv2 " Sergey Senozhatsky
2014-01-15 2:10 ` Minchan Kim [this message]
2014-01-14 9:37 ` [PATCH 3/3] zram: rework reported to end-user zram statistics Sergey Senozhatsky
2014-01-14 10:38 ` Jerome Marchand
2014-01-14 10:57 ` Sergey Senozhatsky
2014-01-14 12:15 ` Jerome Marchand
2014-01-14 12:30 ` Sergey Senozhatsky
2014-01-14 11:10 ` Sergey Senozhatsky
2014-01-14 13:43 ` Jerome Marchand
2014-01-14 13:53 ` Sergey Senozhatsky
2014-01-14 14:02 ` Jerome Marchand
2014-01-14 14:09 ` Sergey Senozhatsky
2014-01-14 14:20 ` Jerome Marchand
2014-01-15 4:24 ` Minchan Kim
2014-01-15 9:10 ` Sergey Senozhatsky
2014-01-14 9:42 ` [PATCH 0/3] zram stats rework and code cleanup Sergey Senozhatsky
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=20140115021051.GH1992@bbox \
--to=minchan@kernel.org \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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).