From owner-freebsd-current@FreeBSD.ORG Fri Oct 28 11:08:15 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E91E416A41F for ; Fri, 28 Oct 2005 11:08:15 +0000 (GMT) (envelope-from djp@polands.org) Received: from corinth.polands.org (CPE-72-129-222-120.new.res.rr.com [72.129.222.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9377F43D45 for ; Fri, 28 Oct 2005 11:08:08 +0000 (GMT) (envelope-from djp@polands.org) Received: from jericho.polands.org (jericho.polands.org [172.16.1.35]) by corinth.polands.org (8.13.4/8.13.4) with ESMTP id j9S4swfE081105 for ; Thu, 27 Oct 2005 23:54:58 -0500 (CDT) (envelope-from djp@polands.org) Received: from jericho.polands.org (localhost [127.0.0.1]) by jericho.polands.org (8.13.4/8.13.1) with ESMTP id j9S4svVf044413 for ; Thu, 27 Oct 2005 23:54:57 -0500 (CDT) (envelope-from djp@jericho.polands.org) Received: (from djp@localhost) by jericho.polands.org (8.13.4/8.13.1/Submit) id j9S4sv9I044412 for freebsd-current@freebsd.org; Thu, 27 Oct 2005 23:54:57 -0500 (CDT) (envelope-from djp) Date: Thu, 27 Oct 2005 23:54:57 -0500 From: Doug Poland To: freebsd-current@freebsd.org Message-ID: <20051028045457.GA44396@polands.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV 0.87/1149/Thu Oct 27 15:20:09 2005 on corinth.polands.org X-Virus-Status: Clean Subject: 6.0 and "options PREEMPTION" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2005 11:08:16 -0000 Hello, I'm confused about 6.0 and the kernel setting "options PREEMPTION". I was reading an article on OS News: http://www.osnews.com/story.php?news_id=10951 in which Robert Watson stated, 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. -- Regards, Doug