Date: Fri, 28 Oct 2005 14:04:37 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Doug Poland <doug@polands.org> Cc: freebsd-current@freebsd.org Subject: Re: 6.0 and "options PREEMPTION" Message-ID: <20051028140301.X20147@fledge.watson.org> In-Reply-To: <20051028045457.GA44396@polands.org> References: <20051028045457.GA44396@polands.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Oct 2005, Doug Poland wrote: > One of the other nice benefits to the SMPVFS work is that > with our fully preemptive 6.x kernel, not holding the Giant > lock over the file system code lets the file system code not > only preempt lower precedence kernel threads, such as > background crypto operations or file system operations, but be > preempted by more timing critical code, such as sound card > interrupts, network I/O, and so on. > > Does this mean that options PREEMPTION is assumed in 6.0? If not, could > someone explain or point me to some docs that will help me understand. In FreeBSD 6.0 and higher, options PREEMPTION appears in the default kernel configuration (GENERIC). When upgrading from earlier revisions, if you keep the same config file, you'll need to add it manually. With the advent of "include" support in newer FreeBSD versions, I find I generally have my own include file include GENERIC, then add nodevice/nooptions to remove things I don't want, and device/options to add things I do want. The SMP kernel configuration is an example of this, as it includes GENERIC but adds SMP. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051028140301.X20147>