From: "Sriram Narasimhan" <nsri@tataelxsi.co.in>
To: linux-kernel@vger.kernel.org
Subject: Problems in kernel memory allocation
Date: Sat, 12 Apr 2003 20:04:44 +0530 [thread overview]
Message-ID: <3E982404.70106@tataelxsi.co.in> (raw)
Hi,
I am having problems allocating more than 2.5 MB in the linux kernel.
I am using Linux 2.4.7-10 RH 7.2 on i386.
Physical RAM: 64 MB
I tried two methods of allocation, one using kmalloc and other using
kmem_cache_alloc. Both of them failed to allocate more than 2.5 MB.
(GFP_KERNEL / GFP_ATOMIC operations)
When I run 'free' I am able to see that the free physical memory is
about 4MB and the free buffers/cache is about 52 MB.
The report is as follows:
total used free shared buffers cached
Mem: 62264 57928 4336 0 30152 17768
-/+ buffers/cache: 10008 52256
Swap: 192772 0 192772
I also found out that the /proc/meminfo had about 43MB of Inact_dirty .
Is there any way to forcefully flush the dirty buffers ?
Why is the allocation consistently failing in about 2.5 or 3MB ?
Only when the free physical is about 30MB and I start allocating am I
able to successfully allocate about 5MB.
Is there a restriction as to how much memory you can allocate in the
kernel ?
Sriram
reply other threads:[~2003-04-12 14:23 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=3E982404.70106@tataelxsi.co.in \
--to=nsri@tataelxsi.co.in \
--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
all inboxes | Powered by JetHome®