From: "Ofer Raz" <oraz@checkpoint.com>
To: "'Arjan van de Ven'" <arjanv@redhat.com>,
"'Ofer Raz'" <oraz@checkpoint.com>
Cc: <wagnerjd@prodigy.net>, <linux-kernel@vger.kernel.org>
Subject: RE: FW: 2.4.9/2.4.18 max kernel allocation size
Date: Wed, 9 Oct 2002 14:06:08 +0200 [thread overview]
Message-ID: <032101c26f8c$413e9440$8b705a3e@checkpoint.com> (raw)
In-Reply-To: <20021008121853.A23798@devserv.devel.redhat.com>
I've done some additional testing.
In order to avoid huge allocations, I've tried allocating 100 blocks of 3MB
each on 2.4.18-10 using vmalloc.
On 1GB physical memory machine I can allocate only 80MB.
When adding memory limit to grub.conf (mem=999M) I get 900MB.
- Ofer
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Arjan van de Ven
Sent: Tuesday, October 08, 2002 6:19 PM
To: Ofer Raz
Cc: 'Arjan van de Ven'; wagnerjd@prodigy.net; linux-kernel@vger.kernel.org
Subject: Re: FW: 2.4.9/2.4.18 max kernel allocation size
On Tue, Oct 08, 2002 at 06:17:17PM +0200, Ofer Raz wrote:
> The following code was used in kernel module & called from IOCTL context
in
> order to test the max allocation size possible:
I think you misunderstood. I was asking for the source
of the PROBLEM you
were having, not the test. You are doing something wrong for needing
such a huge vmalloc area, but without the source (it
is gpl code, right?) nobody can do suggestions on how to improve your code.
>
> #define BLOCK_SIZE xxx
>
> for (size = BLOCK_SIZE; size; size--)
> {
> tmp = vmalloc(size * 1024 * 1024);
>
> if (tmp)
> {
> printk("Allocation of %dMB bytes succeeded!\n", size);
> vfree(tmp);
> break;
> }
> }
>
y
-
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-09 12:01 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 [this message]
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='032101c26f8c$413e9440$8b705a3e@checkpoint.com' \
--to=oraz@checkpoint.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wagnerjd@prodigy.net \
/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;
as well as URLs for NNTP newsgroup(s).