From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Paul Mundt <paul.mundt@nokia.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [RFC] mempool_alloc() pre-allocated object usage
Date: Wed, 5 Oct 2005 18:35:40 -0300 [thread overview]
Message-ID: <20051005213540.GA10123@logos.cnet> (raw)
In-Reply-To: <20051003162122.GB1844@nokia.com>
Hi Paul,
On Mon, Oct 03, 2005 at 07:21:22PM +0300, Paul Mundt wrote:
> On Mon, Oct 03, 2005 at 04:49:13PM +0200, Arjan van de Ven wrote:
> > On Mon, 2005-10-03 at 17:36 +0300, Paul Mundt wrote:
> > > Both usage patterns seem valid from my point of view, would you be open
> > > to something that would accomodate both? (ie, possibly adding in a flag
> > > to determine pre-allocated object usage?) Or should I not be using
> > > mempool for contiguity purposes?
> >
> > a similar dillema was in the highmem bounce code in 2.4; what worked
> > really well back then was to do it both; eg use half the pool for
> > "immediate" use, then try a VM alloc, and use the second half of the
> > pool for the really emergency cases.
> >
> Unfortunately this won't work very well in our case since it's
> specifically high order allocations that we are after, and we don't have
> the extra RAM to allow for this.
Out of curiosity, what is the requirement for higher order pages?
next prev parent reply other threads:[~2005-10-06 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 14:36 [RFC] mempool_alloc() pre-allocated object usage Paul Mundt
2005-10-03 14:49 ` Arjan van de Ven
2005-10-03 16:21 ` Paul Mundt
2005-10-05 21:35 ` Marcelo Tosatti [this message]
2005-10-04 6:59 ` Jens Axboe
2005-10-03 14:59 ` Brian Gerst
2005-10-04 1:06 ` Nick Piggin
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=20051005213540.GA10123@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul.mundt@nokia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.