From: Brian Gerst <bgerst@didntduck.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kmalloc() allocation.
Date: Tue, 31 Oct 2000 01:11:29 -0500 [thread overview]
Message-ID: <39FE6291.FA8162A7@didntduck.org> (raw)
In-Reply-To: <E13qJZL-00076K-00@the-village.bc.nu> <Pine.LNX.3.95.1001030133720.3346A-100000@chaos.analogic.com> <8tll94$hc9$1@cesium.transmeta.com>
"H. Peter Anvin" wrote:
>
> Followup to: <Pine.LNX.3.95.1001030133720.3346A-100000@chaos.analogic.com>
> By author: "Richard B. Johnson" <root@chaos.analogic.com>
> In newsgroup: linux.dev.kernel
> >
> > > 64K probably less. kmalloc allocates physically linear spaces. vmalloc will
> > > happily grab you 2Mb of space but it will not be physically linear
> > >
> >
> > Okay. Thanks.
> >
>
> FWIW, vmalloc()-allocated pages are definitely pinned-down and
> available to interrupts. However, you should keep in mind that the
> vmalloc() call *itself* is quite expensive on SMP machines (have to
> interrupt all CPUs and flush their TLBs!!) so if you're using
> vmalloc(), be careful with the number of calls you make. Of course,
> this is usually not a problem.
This was just changed in 2.4 so that vmalloced pages are faulted in on
demand.
--
Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-31 6:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 15:57 Richard B. Johnson
2000-10-30 16:06 ` Tigran Aivazian
2000-10-30 16:28 ` Richard B. Johnson
2000-10-30 16:38 ` Tigran Aivazian
2000-10-30 17:57 ` Richard B. Johnson
2000-10-30 16:06 ` John Levon
2000-10-30 16:27 ` Richard B. Johnson
2000-10-30 16:49 ` Jeff Garzik
2000-10-30 16:54 ` Tigran Aivazian
2000-10-30 17:08 ` Jeff Garzik
2000-10-30 18:08 ` Richard B. Johnson
2000-10-30 18:06 ` Richard B. Johnson
2000-10-30 18:10 ` Jeff Garzik
2000-10-30 16:40 ` Rik van Riel
2000-10-31 7:03 ` Mike Galbraith
2000-10-31 10:48 ` Ingo Oeser
2000-10-31 13:35 ` Rik van Riel
2000-10-31 13:59 ` Richard B. Johnson
2000-10-31 15:57 ` Pauline Middelink
2000-10-31 15:17 ` Ingo Oeser
2000-10-31 16:11 ` Rik van Riel
2000-10-31 18:22 ` Ingo Oeser
2000-10-31 14:43 ` afei
2000-10-30 18:22 ` Alan Cox
2000-10-30 18:37 ` Richard B. Johnson
2000-10-31 5:28 ` H. Peter Anvin
2000-10-31 6:11 ` Brian Gerst [this message]
2000-10-31 8:44 ` Andi Kleen
2000-10-31 12:58 ` Brian Gerst
2000-10-31 14:48 ` kernel
2000-10-31 15:01 ` Alan Cox
2000-10-31 15:57 ` kernel
2000-10-31 8:49 ` Tigran Aivazian
2000-10-31 8:54 ` Andi Kleen
2000-10-31 9:07 ` Tigran Aivazian
2000-10-31 9:25 ` Andi Kleen
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=39FE6291.FA8162A7@didntduck.org \
--to=bgerst@didntduck.org \
--cc=hpa@zytor.com \
--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
all inboxes | Powered by JetHome®