From owner-freebsd-hackers Sun Sep 20 15:10:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19036 for freebsd-hackers-outgoing; Sun, 20 Sep 1998 15:10:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19027 for ; Sun, 20 Sep 1998 15:10:19 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id QAA03178; Sun, 20 Sep 1998 16:03:22 -0600 (MDT) Date: Sun, 20 Sep 1998 16:03:22 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809202203.QAA03178@narnia.plutotech.com> To: Eivind Eklund cc: hackers@FreeBSD.ORG Subject: Re: malloc()ing 64K physically contiguous buffer in kernel Newsgroups: pluto.freebsd.hackers In-Reply-To: <199809201745.NAA21711@skynet.ctr.columbia.edu> <19980920212910.21253@follo.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980920212910.21253@follo.net> you wrote: > On Sun, Sep 20, 1998 at 01:45:24PM -0400, Bill Paul wrote: >> So: is there some way to allocate 64K of contiguous memory? Or even >> 8/16/32K? As long as I can hit one of the allowed buffer sizes I'll >> be happy, although I wanted 64K in order to reduce the likelyhood of >> receiver overruns. > > contigmalloc(). You should use bus_dma instead of contigmalloc, but I won't think badly of you until I've gotten off my duff and written the man pages for it. (bus_dma eventually uses contigmalloc to satisfy the request, but this may change (very likely on other platforms)). -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message