From: "Ben Israel" <ben@genesis-one.com>
To: <linux-kernel@vger.kernel.org>
Subject: Write allocated mallocs
Date: Tue, 12 Mar 2002 19:41:48 -0500 [thread overview]
Message-ID: <010701c1ca27$dc05fdc0$60d53318@pbc.adelphia.net> (raw)
I have noticed some unexpected behavior of my Linux 2.4.7 kernel. It appears
that my user level task is only allowed 512 mallocs before each malloc
starts getting physical memory. I want to malloc virtual address space and
only get physical memory when I write to a page. Is this some compiled
constant in the kernel? Are there any ways to get more? Where can I read
about such architecture decisions, so other behavior won't be so unexpected?
Ben Israel
next reply other threads:[~2002-03-13 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 0:41 Ben Israel [this message]
2002-03-13 7:11 ` guy keren
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='010701c1ca27$dc05fdc0$60d53318@pbc.adelphia.net' \
--to=ben@genesis-one.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 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®