From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: chandrasekhar nagaraj <chandrasekhar_n@hotmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Preallocation of memory in 2.4 kernels
Date: Fri, 13 Aug 2004 23:09:51 +0100 [thread overview]
Message-ID: <1092434989.25002.30.camel@localhost.localdomain> (raw)
In-Reply-To: <BAY17-F222koAUaQMni0003849e@hotmail.com>
On Gwe, 2004-08-13 at 19:11, chandrasekhar nagaraj wrote:
> We felt that we could preallocate some 64K of memory pool(before the IO
> starts) and then when this kind of small memory request comes (note that
> this request size is variable) , we would use this memory pool instead of
> using the kmalloc.
> Is there any mechanism in 2.4 kernels to achieve this task.?
Yes - use kmalloc or multiple kmallocs before the I/O starts (eg
allocate in the driver startup). 2.6.x has a nice structure for doing
this and helpers but for the general case drivers just preallocate
buffers to be sure they can make progress. It's normally the most
efficient solution anyway.
prev parent reply other threads:[~2004-08-13 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 18:11 Preallocation of memory in 2.4 kernels chandrasekhar nagaraj
2004-08-13 22:09 ` Alan Cox [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=1092434989.25002.30.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=chandrasekhar_n@hotmail.com \
--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 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.