From: "Stephen C. Tweedie" <sct@redhat.com>
To: Roman Mitnitski <roman@checkpoint.com>
Cc: linux-mm@kvack.org
Subject: Re: Allocating large chunks of mem from net-bh
Date: Tue, 25 Jul 2000 14:43:29 +0100 [thread overview]
Message-ID: <20000725144329.F1396@redhat.com> (raw)
In-Reply-To: <00df01bff54f$280d1230$398d96d4@checkpoint.com>; from roman@checkpoint.com on Mon, Jul 24, 2000 at 11:11:26AM +0200
Hi,
On Mon, Jul 24, 2000 at 11:11:26AM +0200, Roman Mitnitski wrote:
>
> 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?
Yep. Just call get_free_page() to allocate as many individual pages
as you want. I assume that if you don't need physical contiguity,
then tracking that set of pages will be fine for you.
kiobufs will provide convenient containers for such sets of pages in
2.4 if you want them, and we're adding things like support
functionality for the allocation of arbitrary pages directly into
kiobufs for 2.5.
Cheers,
Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
prev parent reply other threads:[~2000-07-25 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-24 9:11 Roman Mitnitski
2000-07-25 13:43 ` Stephen C. Tweedie [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=20000725144329.F1396@redhat.com \
--to=sct@redhat.com \
--cc=linux-mm@kvack.org \
--cc=roman@checkpoint.com \
/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