From owner-cvs-all Mon Jan 15 13:39:12 2001 Delivered-To: cvs-all@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 27B0437B6B6; Mon, 15 Jan 2001 13:38:45 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0FLcLs61722; Mon, 15 Jan 2001 14:38:42 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101152138.f0FLcLs61722@aslan.scsiguy.com> To: John Baldwin Cc: Bruce Evans , cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Wilko Bulte , Poul-Henning Kamp , Peter Wemm Subject: Re: cvs commit: src/sys/i386/conf GENERIC In-Reply-To: Your message of "Mon, 15 Jan 2001 13:34:34 PST." Date: Mon, 15 Jan 2001 14:38:21 -0700 From: "Justin T. Gibbs" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> All that is required in the userland implementation is the setting of a >> flag so the userland thread scheduler does not perform a thread switch. >> Having an interrupt fire does not have the same consequences on a userland >> program as it does for the kernel. > >Actually, the process needs to not be switched. This is part of KSE, so you >would have to set a kernel flag in the kse for this, but yes, that would work. > >Granted, it pessimizes the non-i386 case, but not that badly. The kernel trap >to emulate only pessimizes the i386 case (though the 386 could do without extr >a pessimizations, and it is a bigger pessimization.) I suppose I haven't read enough of the KSE stuff to understand why you need to not change processes (or is a process the "unit" used to represent a KSE?). Doesn't the userland scheduler decide what to do with any KSE it is given? Anyway, if you use the "patch up the atomic operation" approach, you don't pessimize anyone except on the first run through a particular atomic operation. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message