From: Minchan Kim <minchan@kernel.org>
To: karam.lee@lge.com
Cc: ngupta@vflare.org, linux-kernel@vger.kernel.org,
matthew.r.wilcox@intel.com, jmarchan@redhat.com,
seungho1.park@lge.com
Subject: Re: [PATCH v2 3/3] zram: implement rw_page operation of zram
Date: Mon, 20 Oct 2014 18:42:02 +0900 [thread overview]
Message-ID: <20141020094202.GC5330@bbox> (raw)
In-Reply-To: <1413190542-23960-4-git-send-email-karam.lee@lge.com>
On Mon, Oct 13, 2014 at 05:55:42PM +0900, karam.lee@lge.com wrote:
> From: "karam.lee" <karam.lee@lge.com>
>
> This patch implements rw_page operation for zram block device.
The description is not good. I know you added lots of words in
cover-letter but this patch is key so it should include more words
as well as cover-letter.
>
> Signed-off-by: karam.lee <karam.lee@lge.com>
> ---
> drivers/block/zram/zram_drv.c | 37 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> index b0c3a20..a44aab0 100644
> --- a/drivers/block/zram/zram_drv.c
> +++ b/drivers/block/zram/zram_drv.c
> @@ -810,8 +810,45 @@ static void zram_slot_free_notify(struct block_device *bdev,
> atomic64_inc(&zram->stats.notify_free);
> }
>
> +static int zram_rw_page(struct block_device *bdev, sector_t sector,
> + struct page *page, int rw)
> +{
> + int offset, ret = 1;
> + u32 index;
> + struct zram *zram;
> + struct bio_vec bv;
> +
> + zram = bdev->bd_disk->private_data;
> + if (!valid_io_request(zram, sector, PAGE_SIZE)) {
> + atomic64_inc(&zram->stats.invalid_io);
-EINVAL?
Otherwise, looks good to me.
Acked-by: Minchan Kim <minchan@kernel.org>
> + goto out;
> + }
> +
> + down_read(&zram->init_lock);
> + if (unlikely(!init_done(zram))) {
> + ret = -ENOMEM;
> + goto out_unlock;
> + }
> +
> + index = sector >> SECTORS_PER_PAGE_SHIFT;
> + offset = sector & (SECTORS_PER_PAGE - 1) << SECTOR_SHIFT;
> +
> + bv.bv_page = page;
> + bv.bv_len = PAGE_SIZE;
> + bv.bv_offset = 0;
> +
> + ret = zram_bvec_rw(zram, &bv, index, offset, rw);
> + page_endio(page, rw, ret);
> +
> +out_unlock:
> + up_read(&zram->init_lock);
> +out:
> + return ret;
> +}
> +
> static const struct block_device_operations zram_devops = {
> .swap_slot_free_notify = zram_slot_free_notify,
> + .rw_page = zram_rw_page,
> .owner = THIS_MODULE
> };
>
> --
> 1.7.9.5
>
> --
> 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
prev parent reply other threads:[~2014-10-20 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 8:55 [PATCH v2 0/3] zram: add rw_page implementation for zram and clean up unnecessary parameter karam.lee
2014-10-13 8:55 ` [PATCH v2 1/3] zram: remove bio parameter from zram_bvec_rw() karam.lee
2014-10-20 9:30 ` Minchan Kim
2014-10-13 8:55 ` [PATCH v2 2/3] zram: change parameter from vaild_io_request() karam.lee
2014-10-20 9:31 ` Minchan Kim
2014-10-13 8:55 ` [PATCH v2 3/3] zram: implement rw_page operation of zram karam.lee
2014-10-20 9:42 ` 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=20141020094202.GC5330@bbox \
--to=minchan@kernel.org \
--cc=jmarchan@redhat.com \
--cc=karam.lee@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.r.wilcox@intel.com \
--cc=ngupta@vflare.org \
--cc=seungho1.park@lge.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