From: Jerome Marchand <jmarchan@redhat.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
Chao Yu <chao2.yu@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3] zram: use notify_free to account all free notifications
Date: Wed, 17 Sep 2014 10:19:29 +0200 [thread overview]
Message-ID: <54194411.6030905@redhat.com> (raw)
In-Reply-To: <1410792568-31539-2-git-send-email-sergey.senozhatsky@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3204 bytes --]
On 09/15/2014 04:49 PM, Sergey Senozhatsky wrote:
> `notify_free' device attribute accounts the number of slot free notifications
> and internally represents the number of zram_free_page() calls. Slot free
> notifications are sent only when device is used as a swap device, hence
> `notify_free' is used only for swap devices. Since f4659d8e620d08 (zram:
> support REQ_DISCARD) ZRAM handles yet another one free notification (also
> via zram_free_page() call) -- REQ_DISCARD requests, which are sent by a
> filesystem, whenever some data blocks are discarded. However, there is no
> way to know the number of notifications in the latter case.
>
> Use `notify_free' to account the number of pages freed by zram_bio_discard()
> and zram_slot_free_notify(). Depending on usage scenario `notify_free'
> represents:
> a) the number of pages freed because of slot free notifications, which is
> equal to the number of swap_slot_free_notify() calls, so there is no
> behaviour change
>
> b) the number of pages freed because of REQ_DISCARD notifications
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Acked-by: Jerome Marchand <jmarchan@redhat.com>
> ---
> Documentation/ABI/testing/sysfs-block-zram | 13 ++++++++-----
> drivers/block/zram/zram_drv.c | 1 +
> 2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-block-zram b/Documentation/ABI/testing/sysfs-block-zram
> index b13dc99..a6148ea 100644
> --- a/Documentation/ABI/testing/sysfs-block-zram
> +++ b/Documentation/ABI/testing/sysfs-block-zram
> @@ -77,11 +77,14 @@ What: /sys/block/zram<id>/notify_free
> Date: August 2010
> Contact: Nitin Gupta <ngupta@vflare.org>
> Description:
> - The notify_free file is read-only and specifies the number of
> - swap slot free notifications received by this device. These
> - notifications are sent to a swap block device when a swap slot
> - is freed. This statistic is applicable only when this disk is
> - being used as a swap disk.
> + The notify_free file is read-only. Depending on device usage
> + scenario it may account a) the number of pages freed because
> + of swap slot free notifications or b) the number of pages freed
> + because of REQ_DISCARD requests sent by bio. The former ones
> + are sent to a swap block device when a swap slot is freed, which
> + implies that this disk is being used as a swap disk. The latter
> + ones are sent by filesystem mounted with discard option,
> + whenever some data blocks are getting discarded.
>
> What: /sys/block/zram<id>/zero_pages
> Date: August 2010
> diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> index d78b245..3b85016 100644
> --- a/drivers/block/zram/zram_drv.c
> +++ b/drivers/block/zram/zram_drv.c
> @@ -698,6 +698,7 @@ static void zram_bio_discard(struct zram *zram, u32 index,
> bit_spin_lock(ZRAM_ACCESS, &meta->table[index].value);
> zram_free_page(zram, index);
> bit_spin_unlock(ZRAM_ACCESS, &meta->table[index].value);
> + atomic64_inc(&zram->stats.notify_free);
> index++;
> n -= PAGE_SIZE;
> }
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-09-17 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 14:49 [PATCHv3] zram: use notify_free to account all free notifications Sergey Senozhatsky
2014-09-15 14:49 ` Sergey Senozhatsky
2014-09-15 23:03 ` Minchan Kim
2014-09-17 8:19 ` Jerome Marchand [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=54194411.6030905@redhat.com \
--to=jmarchan@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chao2.yu@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@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).