From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 4 16:56:00 2007 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 437AC16A417 for ; Thu, 4 Oct 2007 16:56:00 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 3AD2513C45B for ; Thu, 4 Oct 2007 16:55:55 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 193E71A4D8B; Thu, 4 Oct 2007 09:55:55 -0700 (PDT) Date: Thu, 4 Oct 2007 09:55:55 -0700 From: Alfred Perlstein To: Dag-Erling Sm??rgrav Message-ID: <20071004165555.GQ31826@elvis.mu.org> References: <20071003015231.GJ31826@elvis.mu.org> <86zlyzqmgo.fsf@ds4.des.no> <20071004094821.GM31826@elvis.mu.org> <86ejgbqjvr.fsf@ds4.des.no> <20071004101902.GN31826@elvis.mu.org> <863awrqilu.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <863awrqilu.fsf@ds4.des.no> User-Agent: Mutt/1.4.2.3i Cc: hackers@freebsd.org Subject: Re: Critical Sections for userland. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2007 16:56:00 -0000 * Dag-Erling Sm??rgrav [071004 03:28] wrote: > Alfred Perlstein writes: > > It's not worth my time to engage someone with your mind set, you > > posses neither the technical nor interpersonal skill to be useful > > to me. > > This could be the beginning of a wonderful friendship... > > > For context see my replies in this thread to Kip Macy which explains > > how one deals with the false-problems you mention. > > I did read them, and I'm not convinced at all. You are asking for a > large amount of complexity to be added to the system, but you refuse to > tell us what you're actually trying to do. Are you worried that we > might actually figure out a way to do it without raping the scheduler? As already explained by Kip, the goal is to avoid switching out a lock owner due to quantum exhaustion at an inopportune time. We have needs that may wind up not being applicable to FreeBSD, however if we can accomplish this in a way that is not too awful we would likely be sharing the code, no matter how annoying you make it. :) -- - Alfred Perlstein