From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH v5 4/4] zram: introduce zram memory tracking
Date: Fri, 20 Apr 2018 11:18:34 +0900 [thread overview]
Message-ID: <20180420021834.GC6397@jagdpanzerIV> (raw)
In-Reply-To: <20180420020921.GA155841@rodete-desktop-imager.corp.google.com>
On (04/20/18 11:09), Minchan Kim wrote:
[..]
> > hm, OK, can we get this info into the changelog?
>
> No problem. I will add as follows,
>
> "I used the feature a few years ago to find memory hoggers in userspace
> to notice them what memory they have wasted without touch for a long time.
> With it, they could reduce unnecessary memory space. However, at that time,
> I hacked up zram for the feature but now I need the feature again so
> I decided it would be better to upstream rather than keeping it alone.
> I hope I submit the userspace tool to use the feature soon"
Shall we then just wait until you resubmit the "complete" patch set: zram
tracking + the user space tool which would parse the tracking output?
-ss
next prev parent reply other threads:[~2018-04-20 2:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 9:09 [PATCH v5 0/4] zram memory tracking Minchan Kim
2018-04-16 9:09 ` [PATCH v5 1/4] zram: correct flag name of ZRAM_ACCESS Minchan Kim
2018-04-16 9:09 ` [PATCH v5 2/4] zram: mark incompressible page as ZRAM_HUGE Minchan Kim
2018-04-16 9:09 ` [PATCH v5 3/4] zram: record accessed second Minchan Kim
2018-04-16 9:09 ` [PATCH v5 4/4] zram: introduce zram memory tracking Minchan Kim
2018-04-17 21:59 ` Andrew Morton
2018-04-18 1:26 ` Minchan Kim
2018-04-18 21:07 ` Andrew Morton
2018-04-20 2:09 ` Minchan Kim
2018-04-20 2:18 ` Sergey Senozhatsky [this message]
2018-04-20 2:32 ` Minchan Kim
2018-04-20 6:35 ` Minchan Kim
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=20180420021834.GC6397@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=rdunlap@infradead.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