From: Brian Gerst <bgerst@didntduck.org>
To: Paul Mundt <paul.mundt@nokia.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [RFC] mempool_alloc() pre-allocated object usage
Date: Mon, 03 Oct 2005 10:59:54 -0400 [thread overview]
Message-ID: <4341476A.80809@didntduck.org> (raw)
In-Reply-To: <20051003143634.GA1702@nokia.com>
Paul Mundt wrote:
> The downside to this is that some people may be expecting that
> pre-allocated elements are used as reserve space for when regular
> allocations aren't possible. In which case, this would break that
> behaviour.
This is the original intent of the mempool. There must be objects in
reserve so that the machine doesn't deadlock on critical allocations
(ie. disk writes) under memory pressure.
--
Brian Gerst
next prev parent reply other threads:[~2005-10-03 14: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
2005-10-04 6:59 ` Jens Axboe
2005-10-03 14:59 ` Brian Gerst [this message]
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=4341476A.80809@didntduck.org \
--to=bgerst@didntduck.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.