linux-kernel - Re: [PATCH v2 2/2] Memory notification pseudo-device module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 17 Jan 2012 15:32:35 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Leonid Moiseichuk <leonid.moiseichuk@...ia.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	cesarb@...arb.net, kamezawa.hiroyu@...fujitsu.com,
	emunson@...bm.net, aarcange@...hat.com, riel@...hat.com,
	mel@....ul.ie, rientjes@...gle.com, dima@...roid.com,
	gregkh@...e.de, rebecca@...roid.com, san@...gle.com,
	akpm@...ux-foundation.org, vesa.jaaskelainen@...ia.com
Subject: Re: [PATCH v2 2/2] Memory notification pseudo-device module

On Tue, Jan 17, 2012 at 3:22 PM, Leonid Moiseichuk
<leonid.moiseichuk@...ia.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@...ia.com>

Is the point of making this a misc device to keep the ABI compatible
with N9? Is the ABI documented?

                        Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/