From: "Joseph D. Wagner" <wagnerjd@prodigy.net>
To: "'Ofer Raz'" <oraz@checkpoint.com>, <linux-kernel@vger.kernel.org>
Subject: RE: 2.4.9/2.4.18 max kernel allocation size
Date: Tue, 8 Oct 2002 10:35:35 -0500 [thread overview]
Message-ID: <008b01c26ee0$5ee52380$9d893841@joe> (raw)
In-Reply-To: <027801c26ede$0f37deb0$8b705a3e@checkpoint.com>
I might be thinking of something totally different than what you're
talking about, but here it goes:
Change line 18 of mmzone.h from:
#define MAX_ORDER 10
to
#define MAX_ORDER 24
This allows larger contiguous chunks of memory to be allocated, up to
32GB.
I'd be very appreciative if you could send me back whatever statistics
you get as a result of this change. (To be honest, I'm not a good
kernel hacker, and I wanted to gather statistics on this for some time
but don't know how.)
Thanks in advance.
Joseph Wagner
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Ofer Raz
Sent: Tuesday, October 08, 2002 10:19 AM
To: linux-kernel@vger.kernel.org
Subject: FW: 2.4.9/2.4.18 max kernel allocation size
-----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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-10-08 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 15:19 FW: 2.4.9/2.4.18 max kernel allocation size Ofer Raz
2002-10-08 15:27 ` 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 [this message]
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='008b01c26ee0$5ee52380$9d893841@joe' \
--to=wagnerjd@prodigy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oraz@checkpoint.com \
/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.