From owner-freebsd-arm@FreeBSD.ORG Thu Jan 31 15:02:02 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2F688456; Thu, 31 Jan 2013 15:02:02 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id AB591BF4; Thu, 31 Jan 2013 15:02:01 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.6/8.14.6) with ESMTP id r0VF217V023478; Thu, 31 Jan 2013 08:02:01 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.6/8.14.6/Submit) with ESMTP id r0VF21I6023475; Thu, 31 Jan 2013 08:02:01 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 31 Jan 2013 08:02:01 -0700 (MST) From: Warren Block To: Gary Palmer Subject: Re: disk wait mystery In-Reply-To: <20130131142658.GC74563@in-addr.com> Message-ID: References: <20130130001849.7669e033@ivory.lan> <20130130053729.0c9e018f@ivory.lan> <20130130110529.5c5df516@ivory.lan> <8EF6F73D-05AF-4E04-968B-84F35CD0FD85@ugh.net.au> <20130131142658.GC74563@in-addr.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 31 Jan 2013 08:02:01 -0700 (MST) Cc: freebsd-arm@freebsd.org, Brett Wynkoop , Ronald Klop X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 15:02:02 -0000 On Thu, 31 Jan 2013, Gary Palmer wrote: > On Thu, Jan 31, 2013 at 07:12:44AM -0700, Warren Block wrote: >> On Wed, 30 Jan 2013, Andrew wrote: >> >>> On 30 Jan 2013, at 17:05, Brett Wynkoop wrote: >>> >>>> I appreciate the education on this point! I wonder if this should be >>>> considered a man page bug? >>> >>> The man page does say "(or other short term, uninterruptible) wait". I >>> don't know what sort of wait the kernel threads may or may not be in >>> but if they are in one, and its short-term then the man page is >>> correct. Maybe an FAQ entry though. >> >> If the man page is misleading or incomplete, it should be fixed. Based >> on the source, the mention of disk at the start is misleading. Maybe: >> >> D Marks a process in short term, uninterruptible wait. >> >> Or >> >> D Marks a process in short term, uninterruptible wait (typically, >> disk wait). >> >> Which explains the "D" but may reintroduce the confusion. > > D Marks a process in short term, uninterruptible wait (In non-kernel > processes, this is typically waiting on disk I/O) The followup question that creates is "what are kernel threads waiting on?" Which is covered by the uninterruptable part earlier. I think the "typically" handles it without creating more questions. Leaving out the redundant "Marks a process" wording: D Disk wait, or other short-term, uninterruptable wait. "disk wait" was the original term in that man page. "Also shown for uninterruptable kernel threads." is just repeating.