Date: Thu, 1 Jul 2004 12:29:32 -0700 From: Justin Walker <justin@mac.com> To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD and MacOS Message-ID: <FAA25E7E-CB94-11D8-AFC7-00306544D642@mac.com> In-Reply-To: <9B616D82-CB28-11D8-9145-000D9335C6A0@yahoo.com.au> References: <40E1CAAD.3000303@minimum.se> <40E1CF00.2090601@netli.com> <1088557263.3528.102.camel@host-83-146-2-180.bulldogdsl.com> <72A1AE29-CA60-11D8-988E-000A95C969C6@zumbrunn.com> <9B616D82-CB28-11D8-9145-000D9335C6A0@yahoo.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 30, 2004, at 23:33, Q wrote: > > On 30/06/2004, at 4:40 PM, Chris Zumbrunn wrote: > >> >> On 30. Jun 2004, at 3:01, Alasdair Lumsden wrote: >> [snip] > Darwin still uses a Mach kernel design, although Apple has made some > significant modifications to its implementation to reduce message > passing overhead and latency etc, making it something of a hybrid and > no longer a pure micro-kernel. To get pedantic, the Darwin kernel of Mac OS X is not a microkernel. Although it used the code-base of Mach 3.0 as a starting point, it is monolithic, as were the pre-3.0 versions of Mach. In fact, I doubt at this point that you could get any micro-kernel functionality to work based on Darwin. > As a result the Darwin Mach kernel is not the traditional Mach mix of > userspace/kernelspace RPC connected components, instead the kernel is > linked into a single address space, using kernel extensions (loadable > modules) in a similar way FreeBSD does. However these extensions are > implemented using a highly object oriented API (IOKit) for interacting > with the kernel, instead of the traditional struct passing procedural > approach used in FreeBSD. The device driver model (IOKit) is C++, using the "embedded C++" constraints to avoid a huge C++ runtime in the kernel. Other extensions (file system and network plugins), however, are not. > The portions of the FreeBSD kernel that Apple have adopted can be > found as part of the XNU project (the darwin kernel) from Apple's > Opensource website > http://www.opensource.apple.com/darwinsource/ > The CVS tags should still be intact on the files in question. > > While FreeBSD provides a sizable chunk of Darwin's BSDness, it still > has a decent amount of legacy NeXT/BSD code in it as well. I'm not sure precisely what you mean here, but the Darwin kernel has been completely rewritten since the days of NeXT. There may be minor bits of NeXT code left, but I don't think it's much. > Some of the things that have been adopted from FreeBSD/NetBSD in the > Darwin kernel include: > > Crypto support > Filesystem support for CD9660, DEVFS, NFS, VFS, MEMDEV (Curiously this > doesn't include UFS/FFS support) > IP & IPV6 TCP stack support including BPF & IPFW > Most of the BSD/Posix/SYSV system calls (sysctl, fork, exec, ktrace, > mmap, etc) and corresponding MAN pages. Sounds like you've been doing some homework :-} Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | It's not whether you win or lose... | It's whether *I* win or lose. *--------------------------------------*-------------------------------*
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FAA25E7E-CB94-11D8-AFC7-00306544D642>