From owner-freebsd-current Wed Mar 22 12:51:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA14433 for current-outgoing; Wed, 22 Mar 1995 12:51:55 -0800 Received: from post.demon.co.uk (post.demon.co.uk [158.152.1.72]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA14425 for ; Wed, 22 Mar 1995 12:51:52 -0800 Received: from nye1.demon.co.uk by post.demon.co.uk id aa27731; 22 Mar 95 20:48 GMT Date: Wed, 22 Mar 1995 20:48:30 GMT From: Daniel John Nye Reply-To: daniel@nye1.demon.co.uk Message-Id: <268@nye1.demon.co.uk> To: Lambert@nye1.demon.co.uk, Terry@nye1.demon.co.uk, davidg@Root.COM Cc: current@FreeBSD.org, Wollman@nye1.demon.co.uk, Garrett@nye1.demon.co.uk Subject: Re: Re: Why does kern_lkm.c use kmem_alloc()? X-Mailer: FIMail V0.9d X-Anon-Password: diaper Lines: 31 Sender: current-owner@FreeBSD.org Precedence: bulk In your message dated Monday 20, March 1995 you wrote : > >> Can anybody explain why kern_lkm.c uses kmem_alloc() to allocate > >> memory rather than malloc()? Is it just because of the kernel > >> malloc()'s size limit? (I'd really like for it to use malloc so that > >> I could tell how much memory is occupied by LKMs from `vmstat -m'.) > > > >Contiguous driver buffer space for DMA target. > > Contiguous? You mean _physically_ contiguous memory? kmem_alloc() has never > tried to return that. > > -DG > > c00l, but how come i get sent this message.... -- ____ | _ \ __ _ _ __ _ __ _ _ | | | |/ _` | '_ \| '_ \| | | | | | | | ( | | | | | | | | | | | |____/ \__,_|_| |_|_| |_|\__, | *=-=*=-=*=-=*=-=*=-=*=-=*|___/-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=* Baby was a black sheep, baby was a whore.. You know she got big, well she's gonna get bigger.. Baby got her hand got her finger on the trigger, Baby baby baby is a rock & roll niggah! (Outside of society, there's where I wanna be! Outside of society, that's where you'll find me!) --------> BabyDan on IRC ---------> daniel@nye1.demon.co.uk or cs93djn@brunel.ac.uk (Daniel John Nye)