From mboxrd@z Thu Jan 1 00:00:00 1970 From: "KOSAKI Motohiro" Subject: Re: Kernel Event Notifications (was: [RFC] Parallelize IO for e2fsck) Date: Sun, 3 Feb 2008 22:38:04 +0900 Message-ID: <2f11576a0802030538j4ad57469g22a04a7cb54bdcd1@mail.gmail.com> References: <9Mo9w-7Ws-25@gated-at.bofh.it> <20080124234037.GJ15858@mit.edu> <2f11576a0801260432y4405d817p6ef4005d06189654@mail.gmail.com> <200801261655.31313.a1426z@gawab.com> <1201562634.5412.70.camel@jcmlaptop> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Al Boldi" , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, kosaki.motohiro@jp.fujitsu.com To: "Jon Masters" Return-path: In-Reply-To: <1201562634.5412.70.camel@jcmlaptop> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi Jon > I looked at this a year or two back, then ran out of time. But the thing > I wanted to do was have libc's memory allocation routines extended to > handle these through reservations - the kernel should send a userspace > notification and then there should be some kind of concept of returning > memory that's been used for "opportunistic" userspace caching, e.g. in > firefox to cache the last 10 web pages. Let us know how you get on :) sorry for late response. (I didn't notice your mail ;-) You are right... stupid user space caching is very important problem. but I think this is no libc problem. glibc malloc hardly caches the memory. (its default behavior only caching 128K.) but some application use large memory for too opportunistic caching. I understood we need propagandize that using mem_notify to application guys after it merge mainline. I have no idea of solve it easily.