From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: "Jon Masters" <jonathan@jonmasters.org>
Cc: "Al Boldi" <a1426z@gawab.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kosaki.motohiro@jp.fujitsu.com
Subject: Re: Kernel Event Notifications (was: [RFC] Parallelize IO for e2fsck)
Date: Sun, 3 Feb 2008 22:38:04 +0900 [thread overview]
Message-ID: <2f11576a0802030538j4ad57469g22a04a7cb54bdcd1@mail.gmail.com> (raw)
In-Reply-To: <1201562634.5412.70.camel@jcmlaptop>
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.
prev parent reply other threads:[~2008-02-03 13:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9Mo9w-7Ws-25@gated-at.bofh.it>
[not found] ` <9Mo9w-7Ws-23@gated-at.bofh.it>
[not found] ` <9OdWm-7uN-25@gated-at.bofh.it>
[not found] ` <9Oi9A-5EJ-3@gated-at.bofh.it>
[not found] ` <9OiMg-6IC-1@gated-at.bofh.it>
[not found] ` <9OlqL-2xG-3@gated-at.bofh.it>
[not found] ` <9Orda-3ub-45@gated-at.bofh.it>
2008-01-24 17:32 ` [RFC] Parallelize IO for e2fsck Bodo Eggert
[not found] ` <E1JI5vz-0001GG-Vs@be1.7eggert.dyndns.org>
2008-01-24 22:07 ` Andreas Dilger
2008-01-24 23:08 ` Adrian Bunk
2008-01-24 23:40 ` Theodore Tso
2008-01-25 0:25 ` Zan Lynx
2008-01-25 11:09 ` Andreas Dilger
2008-01-26 0:55 ` Zan Lynx
2008-01-26 11:56 ` KOSAKI Motohiro
2008-01-25 18:03 ` Bryan Henderson
2008-01-25 23:01 ` Bodo Eggert
2008-01-26 1:55 ` Bryan Henderson
2008-01-26 13:21 ` Theodore Tso
2008-01-26 12:32 ` KOSAKI Motohiro
[not found] ` <2f11576a0801260432y4405d817p6ef4005d06189654@mail.gmail.com>
2008-01-26 13:55 ` Kernel Event Notifications (was: [RFC] Parallelize IO for e2fsck) Al Boldi
2008-01-26 16:01 ` KOSAKI Motohiro
2008-01-28 23:23 ` Jon Masters
[not found] ` <1201562634.5412.70.camel@jcmlaptop>
2008-02-03 13:38 ` KOSAKI Motohiro [this message]
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=2f11576a0802030538j4ad57469g22a04a7cb54bdcd1@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=a1426z@gawab.com \
--cc=jonathan@jonmasters.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).