From: Eli Carter <eli.carter@inet.com>
To: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: kmalloc(GFP_KERNEL) vs buffer cache
Date: Fri, 09 Nov 2001 13:15:33 -0600 [thread overview]
Message-ID: <3BEC2B55.E7873035@inet.com> (raw)
All,
In dealing with a 2.2 kernel, I'm seeing what appears to be a
kmalloc(GFP_KERNEL) failing to allocate memory because the buffer cache
is using most of available RAM. There are about 5k allocations of about
2k each, done in a loop in an ioctl case (so it is in process context).
It looks like about 3MB of them succeed before one fails.
Is this hypothesis reasonable or not? Why?
According to LDD, GFP_KERNEL will try to swap to get memory if
needed--If that is the case, why would it fail to get memory from the
buffer cache?
What is the correct way to allocate a large number of (relatively) small
buffers? Did this change between 2.2 and 2.4?
TIA,
Eli
--------------------. Real Users find the one combination of bizarre
Eli Carter \ input values that shuts down the system for days.
eli.carter(a)inet.com `-------------------------------------------------
reply other threads:[~2001-11-09 19:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BEC2B55.E7873035@inet.com \
--to=eli.carter@inet.com \
--cc=kernelnewbies@nl.linux.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