Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757651AbYBJBbL (ORCPT ); Sat, 9 Feb 2008 20:31:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753340AbYBJBaz (ORCPT ); Sat, 9 Feb 2008 20:30:55 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:2067 "EHLO spitz.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756222AbYBJBay (ORCPT ); Sat, 9 Feb 2008 20:30:54 -0500 Date: Sun, 10 Feb 2008 01:30:47 +0000 From: Pavel Machek To: Jon Masters Cc: KOSAKI Motohiro , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Marcelo Tosatti , Daniel Spang , Rik van Riel , Andrew Morton , Alan Cox , "linux-fsdevel@vger.kernel.org" , Al Boldi , Zan Lynx Subject: Re: [sample] mem_notify v6: usage example Message-ID: <20080210013047.GB4618@ucw.cz> References: <2f11576a0802090755n123c9b7dh26e0af6a2fef28af@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 775 Lines: 19 On Sat 2008-02-09 11:07:09, Jon Masters wrote: > This really needs to be triggered via a generic kernel > event in the final version - I picture glibc having a > reservation API and having generic support for freeing > such reservations. Not sure what you are talking about. This seems very right to me. We want memory-low notification, not yet another generic communication mechanism. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/