The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Ofer Raz" <oraz@checkpoint.com>
To: <linux-kernel@vger.kernel.org>
Subject: FW: 2.4.9/2.4.18 max kernel allocation size
Date: Tue, 8 Oct 2002 17:19:12 +0200	[thread overview]
Message-ID: <027801c26ede$0f37deb0$8b705a3e@checkpoint.com> (raw)



-----Original Message-----
From: Ofer Raz [mailto:oraz@checkpoint.com]
Sent: Tuesday, October 08, 2002 2:19 PM
To: 'linux-kernel-owner@vger.kernel.org'
Subject: 2.4.9/2.4.18 max kernel allocation size


I'm trying to obtain the largest kernel allocation possible using vmalloc.

I have tested both Linux 2.4.9-7 and 2.4.18-10 max kernel allocation using
vmalloc on Intel platform with different physical memory configurations.
>From my experience, playing with the Virtual/Physical memory split issues
different results (which makes sense)

Following are the results on 2.4.9-7 when the 4GB highmem config option is
set:

Config Option	Physical Memory	Max Allocation
CONFIG_1GB		512MB			400
			1024MB		900
			1536MB		1400
			2048MB		981

CONFIG_2GB		512MB			400
			1024MB		900
			1536MB		461
			2048MB		VFS Panic on boot

CONFIG_3GB		512MB			400
			1024MB		85
			1536MB		VFS Panic on boot
			2048MB		VFS Panic on boot

Please note that CONFIG_3GB is the default and results 85MB max allocation
for 1GB machine.

For my surprise, I have discovered that the CONFIG_1GB/CONFIG_2GB/CONFIG_3GB
configuration options were removed from 2.4.18-10, it seems that the kernel
is set for the CONFIG_3GB option (by looking at the PAGE_OFFSET mask
(0xc0000000)).

Any idea how can I make the kernel allocation on 2.4.18-10 larger than 85MB
on 1GB machine?

Cheers,
	Ofer


             reply	other threads:[~2002-10-08 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 15:19 Ofer Raz [this message]
2002-10-08 15:27 ` FW: 2.4.9/2.4.18 max kernel allocation size Arjan van de Ven
     [not found]   ` <028101c26ee6$2c9ec010$8b705a3e@checkpoint.com>
2002-10-08 16:18     ` Arjan van de Ven
2002-10-09 12:06       ` Ofer Raz
2002-10-08 15:35 ` Joseph D. Wagner
2002-10-09 10:22   ` Gianni Tedesco

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='027801c26ede$0f37deb0$8b705a3e@checkpoint.com' \
    --to=oraz@checkpoint.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