From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 23:27:26 2004 Return-Path: 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 63DA616A4CE for ; Sun, 4 Jan 2004 23:27:26 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ADBE43D31 for ; Sun, 4 Jan 2004 23:27:25 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 5CB2772DBF; Sun, 4 Jan 2004 23:27:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 5AE6572DB5; Sun, 4 Jan 2004 23:27:25 -0800 (PST) Date: Sun, 4 Jan 2004 23:27:25 -0800 (PST) From: Doug White To: "Bjoern A. Zeeb" In-Reply-To: Message-ID: <20040104232453.V77465@carver.gumbysoft.com> References: <20040104205911.S77465@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Expensive timeout(9) function ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 05 Jan 2004 07:27:26 -0000 On Mon, 5 Jan 2004, Bjoern A. Zeeb wrote: > On Sun, 4 Jan 2004, Doug White wrote: > > > > what reports do you expect with the > > > > > > "Expensive timeout(9) function" > > > > > > message ? Why do we see it ? > > > > You compiled your kernel with 'options DIAGNOSTIC'. Unless you have an > > explicit reason for doing so, you should not use this option. > > I do have. > > Some people added the code for a special purpose I guess - most likely to > identify something ? So the question is what's the purpose and > if people who compile with DIAGNOSTIC and see it should they report it > and if so what should they report ? I suspect its some code to check for functions that abuse timeouts for long-lasting operations, since no other timeouts can fire while they are called (I think). You'll have to check the commit logs to see exactly why that was added. In any case, unless you're having a problem, we're not interested in any reports of any abnormal behavior when running with DIAGNOSTIC enabled. Use At Your Own Risk. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org