From: Stephen Frost <sfrost@snowman.net>
To: "Shipman, Jeffrey E" <jeshipm@sandia.gov>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Using large amounts of memory in the kernel
Date: Tue, 16 Jul 2002 11:32:30 -0400 [thread overview]
Message-ID: <20020716153230.GE653@ns> (raw)
In-Reply-To: <03781128C7B74B4DBC27C55859C9D73809840661@es06snlnt>
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
* Shipman, Jeffrey E (jeshipm@sandia.gov) wrote:
> I've got a hash table of packet manipulation information
> I need to use inside of a module in my kernel. The problem
> is that this hash table is around 2MB. I'm trying to figure
> out ways to shrink this table, but I'm coming up short on
> ideas. What would be a good way to be able to allocate enough
> memory to store all of this information?
At a guess I'd say vmalloc...
Stephen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-07-16 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 15:22 Using large amounts of memory in the kernel Shipman, Jeffrey E
2002-07-16 15:32 ` Stephen Frost [this message]
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=20020716153230.GE653@ns \
--to=sfrost@snowman.net \
--cc=jeshipm@sandia.gov \
--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