lkml.org 
[lkml]   [2000]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kmalloc() allocation.
On Tue, 31 Oct 2000, Brian Gerst wrote:

> "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.

what do you mean?! That is, of course, impossible because it would break
all existing software, so I won't even bother checking the code, safely
assuming that you perhaps meant something else, ok?

Thanks,
Tigran

-
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/

\
 
 \ /
  Last update: 2005-03-22 12:45    [W:0.291 / U:0.784 seconds]
©2003-2014 Jasper Spaans. Advertise on this site