From: "Roman Mitnitski" <roman@checkpoint.com>
To: linux-mm@kvack.org
Subject: Allocating large chunks of mem from net-bh
Date: Mon, 24 Jul 2000 11:11:26 +0200 [thread overview]
Message-ID: <00df01bff54f$280d1230$398d96d4@checkpoint.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
Hi.
I need to allocate (dynamically, as the need arises) large memory areas
from the bottom-half context (net-bh, to be exact) in Linux 2.2.x.
kmalloc does not let me allocate as much memory as I need, and
vmalloc refuses to work in bottom-half context.
I don't need anything special from the allocated memory, (like physical continuity,
or DMA area). I even don't care much how long
it takes to allocate, sice it really does not happen that much often.
Is there any reasonable workaround that would let me solve this problem?
Is the situation in 2.4 any better (because my code will have to move on to 2.4
eventually)
Roman
[-- Attachment #2: Type: text/html, Size: 1884 bytes --]
next reply other threads:[~2000-07-24 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-24 9:11 Roman Mitnitski [this message]
2000-07-25 13:43 ` Stephen C. Tweedie
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='00df01bff54f$280d1230$398d96d4@checkpoint.com' \
--to=roman@checkpoint.com \
--cc=linux-mm@kvack.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