From owner-freebsd-current@FreeBSD.ORG  Sun Oct  8 23:03:44 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
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 3C25716A501
	for <freebsd-current@freebsd.org>; Sun,  8 Oct 2006 23:03:44 +0000 (UTC)
	(envelope-from asmrookie@gmail.com)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8481843D73
	for <freebsd-current@freebsd.org>; Sun,  8 Oct 2006 23:03:40 +0000 (GMT)
	(envelope-from asmrookie@gmail.com)
Received: by wx-out-0506.google.com with SMTP id i27so1341197wxd
	for <freebsd-current@freebsd.org>; Sun, 08 Oct 2006 16:03:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=UZG6NI+8xobMuPERnWPv1dtpsm6PdI6iUvhHyRWxNT+Efv2D0Yj9LZGSEDoRjgCN2HUiJWecIRLZAH2gsfEI0fYNUdwtGQBh/Z15YDNToNpmDg9wvpcPccb5CQ7ZB8uWTKG20urDdTTyPH6PhmSXSxEaWaG0cJ1lXdD3NFCPlPo=
Received: by 10.70.90.18 with SMTP id n18mr9982102wxb;
	Sun, 08 Oct 2006 16:03:39 -0700 (PDT)
Received: by 10.70.11.4 with HTTP; Sun, 8 Oct 2006 16:03:39 -0700 (PDT)
Message-ID: <3bbf2fe10610081603r1161ac38h4b679e452b6849f6@mail.gmail.com>
Date: Mon, 9 Oct 2006 01:03:39 +0200
From: "Attilio Rao" <attilio@freebsd.org>
Sender: asmrookie@gmail.com
To: "Kip Macy" <kmacy@fsmware.com>, 
	"John-Mark Gurney" <gurney_j@resnet.uoregon.edu>, 
	"David Xu" <davidxu@freebsd.org>, freebsd-current@freebsd.org, 
	"Ivan Voras" <ivoras@fer.hr>
In-Reply-To: <20061008155817.G29803@demos.bsdclusters.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com>
	<20061008135031.G83537@demos.bsdclusters.com>
	<4529667D.8070108@fer.hr> <200610090634.31297.davidxu@freebsd.org>
	<20061008225150.GK793@funkthat.com>
	<3bbf2fe10610081555r67265368sf7f12edbf35bff0d@mail.gmail.com>
	<20061008155817.G29803@demos.bsdclusters.com>
X-Google-Sender-Auth: 9ed116dae8f6e220
Cc: 
Subject: Re: [PATCH] MAXCPU alterable in kernel config - needs testers
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Oct 2006 23:03:44 -0000

2006/10/9, Kip Macy <kmacy@fsmware.com>:
> >
> > How would you see a sched_lock decomposition (and, if it is possible,
> > how many locks it could be decomposed in?)
>
> Rather than having a per thread lock, Solaris uses the lock for the
> current container that a thread is associated with (cpu, run queue,
> sleep queue, etc.) to serialize thread updates. I think this is probably
> the best approach. A per proess spin lock would not scale well for large
> multi-threaded apps.

Yes, this is what I was thinking to.
Maybe sched_lock could be reworked when all the other issues about
SMPng would be closed.
IIRC, somebody was speaking about the starting of a new project which
was related to the analisys and decomposition of the more contentive
locks.

Attilio


-- 
Peace can only be achieved by understanding - A. Einstein