From: Hilik Stein <hilik@netvision.net.il>
To: linux-mips@linux-mips.org
Subject: allocating a large memory area
Date: Wed, 12 Mar 2003 13:28:02 +0200 [thread overview]
Message-ID: <438113fe62.3fe6243811@netvision.net.il> (raw)
Hi All
i am building a kernel based fast packet handler which runs on kernel
2.4.20.
my code resides inside the kernel, which is running on sb1 core.
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.
is this safe ? anything i need to consider before moving forward with that
approach ?
thanks
Hilik
next reply other threads:[~2003-03-12 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 11:28 Hilik Stein [this message]
2003-03-13 0:03 ` allocating a large memory area Ralf Baechle
2003-03-13 0:23 ` Bradley D. LaRonde
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=438113fe62.3fe6243811@netvision.net.il \
--to=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