From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: minchan@kernel.org
Cc: akpm@linux-foundation.org, ddstreet@ieee.org, gunho.lee@lge.com,
iamjoonsoo.kim@lge.com, jmarchan@redhat.com, juno.choi@lge.com,
mel@csn.ul.ie, ngupta@vflare.org, semenzato@google.com,
sergey.senozhatsky@gmail.com, sjennings@variantweb.net,
mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: + zram-support-compaction.patch added to -mm tree
Date: Thu, 5 Mar 2015 20:43:23 +0900 [thread overview]
Message-ID: <20150305114322.GA623@swordfish> (raw)
In-Reply-To: <20150305052941.GK14927@swordfish>
On (03/05/15 14:29), Sergey Senozhatsky wrote:
> On (03/04/15 14:02), akpm@linux-foundation.org wrote:
> > +What: /sys/block/zram<id>/compact
> > +Date: August 2015
> > +Contact: Minchan Kim <minchan@kernel.org>
> > +Description:
> > + The compact file is write-only and trigger compaction for
> > + allocator zrm uses. The allocator moves some objects so that
> > + it could free fragment space.
> > +
> > +What: /sys/block/zram<id>/num_migrated
> > +Date: August 2015
> > +Contact: Minchan Kim <minchan@kernel.org>
> > +Description:
> > + The compact file is read-only and shows how many object
> > + migrated by compaction.
> Minchan, do you want to provide num_migrated as part of zsmalloc stats rather
> than having yet another zram attr? we already provide zsmalloc stats and this
> type of information seems to belong there. just idea.
>
can compaction memory gain be calculated as, for example,
mem_used_total #before_compaction - mem_used_total #after_compaction ?
if yes, then do we need this attr at all?
the other thing is - why does this attr return the sum of all compactions?
wouldn't it be more informative to return the number of bytes gained after
the most recent compaction? but, once again, is this attr worth having?
-ss
next prev parent reply other threads:[~2015-03-05 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54f780fc.3sOWZKr7rufmI85r%akpm@linux-foundation.org>
2015-03-05 0:18 ` + zram-support-compaction.patch added to -mm tree Sergey Senozhatsky
2015-03-05 0:30 ` Minchan Kim
2015-03-05 5:29 ` Sergey Senozhatsky
2015-03-05 11:43 ` Sergey Senozhatsky [this message]
2015-03-09 0:49 ` Minchan Kim
2015-03-09 0:57 ` Sergey Senozhatsky
2015-03-09 1:05 ` Minchan Kim
2015-03-09 1:27 ` Sergey Senozhatsky
2015-03-09 1:47 ` Minchan Kim
2015-03-09 2:07 ` Sergey Senozhatsky
2015-03-09 2:21 ` Minchan Kim
2015-03-09 6:48 ` Sergey Senozhatsky
2015-03-09 14:56 ` Minchan Kim
2015-03-10 5:37 ` 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=20150305114322.GA623@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=gunho.lee@lge.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jmarchan@redhat.com \
--cc=juno.choi@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=semenzato@google.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sjennings@variantweb.net \
/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).