From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anton Vorontsov Subject: Re: [PATCH 1/2] vmpressure: in-kernel notifications Date: Tue, 23 Apr 2013 17:01:49 -0400 Message-ID: <20130423210149.GA9019@teo> References: <1366705329-9426-1-git-send-email-glommer@openvz.org> <1366705329-9426-2-git-send-email-glommer@openvz.org> <20130423202446.GA2484@teo> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20130423202446.GA2484@teo> Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Glauber Costa Cc: linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andrew Morton , Dave Chinner , John Stultz , Joonsoo Kim , Michal Hocko , Kamezawa Hiroyuki , Johannes Weiner On Tue, Apr 23, 2013 at 04:24:46PM -0400, Anton Vorontsov wrote: [...] > > /** > > + * vmpressure_register_kernel_event() - Register kernel-side notification > > Why don't we need the unregister function? I see that the memcg portion > deals with dangling memcgs, but do they dangle forver? Oh, I got it. vmpressure_unregister_event() will unregister all the events anyway. Cool. Thanks! Anton