From: Rik van Riel <riel@conectiva.com.br>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, Benjamin LaHaise <bcrl@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mempool design
Date: Mon, 17 Dec 2001 22:32:53 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0112172232180.15741-100000@imladris.surriel.com> (raw)
In-Reply-To: <20011217165845.C2431@athlon.random>
On Mon, 17 Dec 2001, Andrea Arcangeli wrote:
> On Mon, Dec 17, 2001 at 06:21:53PM +0100, Ingo Molnar wrote:
> > On Mon, 17 Dec 2001, Andrea Arcangeli wrote:
> >
> > > This whole long thread can be resumed in two points:
> > >
> > > 1 mempool reserved memory is "wasted" i.e. not usable as cache
> >
> > reservations, as in Ben's published (i know, incomplete) implementation,
> > are 'wasted' as well.
>
> yes, I was referring only about his long term design arguments.
Long term design arguments don't have to make the short-term
implementation any more complex. I guess you presented a nice
argument to go with the more flexible solution.
cheers,
Rik
--
Shortwave goes a long way: irc.starchat.net #swl
http://www.surriel.com/ http://distro.conectiva.com/
next prev parent reply other threads:[~2001-12-18 0:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 19:40 mempool design Ingo Molnar
2001-12-15 18:47 ` Benjamin LaHaise
2001-12-15 22:18 ` Ingo Molnar
2001-12-17 15:04 ` Andrea Arcangeli
2001-12-17 15:38 ` Victor Yodaiken
2001-12-17 16:10 ` Andrea Arcangeli
2001-12-17 17:33 ` kernel panic Geoffrey
2001-12-18 16:55 ` mempool design Ingo Molnar
2001-12-18 16:06 ` Victor Yodaiken
2001-12-17 17:21 ` Ingo Molnar
2001-12-17 15:58 ` Andrea Arcangeli
2001-12-18 0:32 ` Rik van Riel [this message]
2001-12-18 15:21 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-12-15 9:01 Ingo Molnar
2001-12-15 15:39 ` Rik van Riel
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=Pine.LNX.4.33L.0112172232180.15741-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=andrea@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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).