From owner-freebsd-current Mon Aug 27 11:14:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DC00937B401 for ; Mon, 27 Aug 2001 11:14:34 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.5/8.11.5) with SMTP id f7RIEHP43711; Mon, 27 Aug 2001 14:14:18 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 27 Aug 2001 14:14:16 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bruce Evans Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: KSE kernel comparissons In-Reply-To: <20010827170927.V23439-100000@besplex.bde.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 27 Aug 2001, Bruce Evans wrote: > How much faster (or slower) will it be for threaded programs (for > various numbers of CPUs)? I don't see how it can be faster for a single > CPU (interrupt threads in the kernel show that using threads tends to > pessimize both efficiency and latency for a single CPU). Note that we won't be able to see some of the impactmpacted until SMPng is further along, where KSE will pessimize a number of single-thread operations. For example, right now SMPng proc locking relies on certain proc structure entries being changed only by curproc, meaning that locks are held for reading only by other processes. With KSE, we'll need to actually hold real locks when acting on those curproc entries (in particular, reads) which may impose a substantial performance overhead. I would anticipate that a number of the other potential shortcuts in SMPng would be similarly impacted by KSE. However, since SMPng is very much a work in progress right now, that's not something I think we can quantify yet. This general issue does raise a lot of concerns however -- many locking assumptions in SMPng will need to be changed, and the locking will need to be much more thorough before we can move forward. Even pre-SMPng, we've had race issues relating to unexpected sleeps, this will only get more hairy (although architecturally better) with SMPng. I'm worried that throwing KSE into the mix is going to hurt a lot. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message