From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Hilik Stein" <hilik@netvision.net.il>
Cc: <linux-mips@linux-mips.org>
Subject: Re: allocating a large memory area
Date: Wed, 12 Mar 2003 19:23:26 -0500 [thread overview]
Message-ID: <01fe01c2e8f6$c41451a0$6601010a@prefect> (raw)
In-Reply-To: 438113fe62.3fe6243811@netvision.net.il
----- Original Message -----
From: "Hilik Stein" <hilik@netvision.net.il>
To: <linux-mips@linux-mips.org>
Sent: Wednesday, March 12, 2003 6:28 AM
Subject: allocating a large memory area
> i need to allocate a large memory region for my data (32MB), which is far
> beyond what kmalloc can provide for me.
> i do not want to use vmalloc, since it will allocate the memory out of
> KSEG2, which is too slow and will generate too many exceptions when i
> have to access my data randomly.
> i was thinking of limiting the linux from accessing the highest physical
> 32MB by using "mem=224M" kernel command line parameter. this was i
> can access my data using 0x8e000000 through KSEG1.
Or put it below the kernel load point.
Or... I've used this trick - define a large array and let the linker make
space for it in .bss. This is convenient since now the kernel has no
special requirement about load address or memory limit and the address can
just be a pointer to the array.
Regards,
Brad
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Hilik Stein <hilik@netvision.net.il>
Cc: linux-mips@linux-mips.org
Subject: Re: allocating a large memory area
Date: Wed, 12 Mar 2003 19:23:26 -0500 [thread overview]
Message-ID: <01fe01c2e8f6$c41451a0$6601010a@prefect> (raw)
Message-ID: <20030313002326.IoiKp1AF1I8NfNgdexM34skWXzz5h6XYDaCviDnkf-c@z> (raw)
In-Reply-To: 438113fe62.3fe6243811@netvision.net.il
----- Original Message -----
From: "Hilik Stein" <hilik@netvision.net.il>
To: <linux-mips@linux-mips.org>
Sent: Wednesday, March 12, 2003 6:28 AM
Subject: allocating a large memory area
> i need to allocate a large memory region for my data (32MB), which is far
> beyond what kmalloc can provide for me.
> i do not want to use vmalloc, since it will allocate the memory out of
> KSEG2, which is too slow and will generate too many exceptions when i
> have to access my data randomly.
> i was thinking of limiting the linux from accessing the highest physical
> 32MB by using "mem=224M" kernel command line parameter. this was i
> can access my data using 0x8e000000 through KSEG1.
Or put it below the kernel load point.
Or... I've used this trick - define a large array and let the linker make
space for it in .bss. This is convenient since now the kernel has no
special requirement about load address or memory limit and the address can
just be a pointer to the array.
Regards,
Brad
next prev parent reply other threads:[~2003-03-13 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 11:28 allocating a large memory area Hilik Stein
2003-03-13 0:03 ` Ralf Baechle
2003-03-13 0:23 ` Bradley D. LaRonde [this message]
2003-03-13 0:23 ` Bradley D. LaRonde
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='01fe01c2e8f6$c41451a0$6601010a@prefect' \
--to=brad@ltc.com \
--cc=hilik@netvision.net.il \
--cc=linux-mips@linux-mips.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