From: <leonid.moiseichuk@nokia.com>
To: penberg@kernel.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
cesarb@cesarb.net, kamezawa.hiroyu@jp.fujitsu.com,
emunson@mgebm.net, aarcange@redhat.com, riel@redhat.com,
mel@csn.ul.ie, rientjes@google.com, dima@android.com,
gregkh@suse.de, rebecca@android.com, san@google.com,
akpm@linux-foundation.org, vesa.jaaskelainen@nokia.com
Subject: RE: [PATCH v2 2/2] Memory notification pseudo-device module
Date: Tue, 17 Jan 2012 13:45:51 +0000 [thread overview]
Message-ID: <84FF21A720B0874AA94B46D76DB9826904559397@008-AM1MPN1-003.mgdnok.nokia.com> (raw)
In-Reply-To: <CAOJsxLFCbF8azY48_SHhYQ0oRDrf2-rEvGMKHBne2Znpj0XL4g@mail.gmail.com>
Not only, here is many reasons:
1. publish code for review by people who knows how to do things and who can advise something valuable
2. to have one more update source in addition to memcg I used in n9 for libmemnotify and which works not I like to see (ideally drop memcg)
3. maybe someone needs similar solution, keep it internally = kill it. Now module looks pretty simple for me and maintainable. Plus one small issue fixed for swapinfo()
So at least now it could be used for tracking activity and it is a good improvement. It also could be extended to report "memory pressure value" similar to Minchan's patch does if necessary.
With Best Wishes,
Leonid
> -----Original Message-----
> From: penberg@gmail.com [mailto:penberg@gmail.com] On Behalf Of ext
> Pekka Enberg
> Sent: 17 January, 2012 15:33
> To: Moiseichuk Leonid (Nokia-MP/Helsinki)
> Cc: linux-mm@kvack.org; linux-kernel@vger.kernel.org; cesarb@cesarb.net;
> kamezawa.hiroyu@jp.fujitsu.com; emunson@mgebm.net;
> aarcange@redhat.com; riel@redhat.com; mel@csn.ul.ie;
> rientjes@google.com; dima@android.com; gregkh@suse.de;
> rebecca@android.com; san@google.com; akpm@linux-foundation.org;
> Jaaskelainen Vesa (Nokia-MP/Helsinki)
> Subject: Re: [PATCH v2 2/2] Memory notification pseudo-device module
>
> On Tue, Jan 17, 2012 at 3:22 PM, Leonid Moiseichuk
> <leonid.moiseichuk@nokia.com> wrote:
> > The memory notification (memnotify) device tracks level of memory
> > utilization, active page set and notifies subscribed processes when
> > consumption crossed specified threshold(s) up or down. It could be
> > used on embedded devices to implementation of performance-cheap
> memory
> > reacting by using e.g. libmemnotify or similar user-space component.
> >
> > The minimal (250 ms) and maximal (15s) periods of reaction and
> > granularity (~1.4% of memory size) could be tuned using module options.
> >
> > Signed-off-by: Leonid Moiseichuk <leonid.moiseichuk@nokia.com>
>
> Is the point of making this a misc device to keep the ABI compatible with N9?
> Is the ABI documented?
>
> Pekka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-01-17 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 13:22 [PATCH v2 0/2] " Leonid Moiseichuk
2012-01-17 13:22 ` [PATCH v2 1/2] Making si_swapinfo exportable Leonid Moiseichuk
2012-01-18 10:34 ` Pekka Enberg
2012-01-18 14:09 ` Greg KH
2012-01-18 14:46 ` Konrad Rzeszutek Wilk
2012-01-18 15:00 ` Greg KH
2012-01-18 14:47 ` leonid.moiseichuk
2012-01-18 15:00 ` Greg KH
2012-01-18 15:20 ` Pekka Enberg
2012-01-17 13:22 ` [PATCH v2 2/2] Memory notification pseudo-device module Leonid Moiseichuk
2012-01-17 13:32 ` Pekka Enberg
2012-01-17 13:45 ` leonid.moiseichuk [this message]
2012-01-17 13:58 ` Pekka Enberg
2012-01-17 14:28 ` leonid.moiseichuk
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=84FF21A720B0874AA94B46D76DB9826904559397@008-AM1MPN1-003.mgdnok.nokia.com \
--to=leonid.moiseichuk@nokia.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cesarb@cesarb.net \
--cc=dima@android.com \
--cc=emunson@mgebm.net \
--cc=gregkh@suse.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=penberg@kernel.org \
--cc=rebecca@android.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=san@google.com \
--cc=vesa.jaaskelainen@nokia.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