From owner-freebsd-hackers Thu Aug 7 15:29:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA04388 for hackers-outgoing; Thu, 7 Aug 1997 15:29:43 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA04356; Thu, 7 Aug 1997 15:29:33 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wwb3d-0006cv-00; Thu, 7 Aug 1997 16:29:25 -0600 To: Darren Reed Subject: Re: cvs commit: src/sys/vm vm_zone.c vm_zone.h Cc: dyson@freebsd.org, hackers@freebsd.org In-reply-to: Your message of "Fri, 08 Aug 1997 07:47:21 +1000." <199708072147.HAA10870@plum.cyber.com.au> References: <199708072147.HAA10870@plum.cyber.com.au> Date: Thu, 07 Aug 1997 16:29:24 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199708072147.HAA10870@plum.cyber.com.au> Darren Reed writes: : For starters, there are bcopy, strcmp, , etc (libkern - section 9l ?). : : Also there is copyin and copyout, malloc and free. Hmmm, do things like : MALLOC() get documented and `approved' as the kernel interface for malloc : rather than malloc itself ? Not to mention things like bread, bwrite, which are useful for stacked device drivers. And just whatis the difference between bwrite and bdwrite anyway (I just checked the code, but it would be useful to know w/o doing this). Or are these interfaces too subject to change to document. I know that Solaris doesn't even document them... Warner