From owner-freebsd-current@FreeBSD.ORG  Sat Mar 28 00:08:42 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CF61E106564A;
	Sat, 28 Mar 2009 00:08:42 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id A9CD78FC17;
	Sat, 28 Mar 2009 00:08:42 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
	by cyrus.watson.org (Postfix) with ESMTPS id 360CC46B45;
	Fri, 27 Mar 2009 20:08:42 -0400 (EDT)
Date: Sat, 28 Mar 2009 00:08:42 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
In-Reply-To: <7362.1238195438@critter.freebsd.dk>
Message-ID: <alpine.BSF.2.00.0903280006510.12518@fledge.watson.org>
References: <7362.1238195438@critter.freebsd.dk>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Sergey Babkin <babkin@verizon.net>, freebsd-hackers@FreeBSD.org,
	attilio@FreeBSD.org, freebsd-current@FreeBSD.org,
	prashant.vaibhav@gmail.com
Subject: Re: Improving the kernel/i386 timecounter performance (GSoC
	proposal)
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: Sat, 28 Mar 2009 00:08:43 -0000

On Fri, 27 Mar 2009, Poul-Henning Kamp wrote:

> In message <alpine.BSF.2.00.0903272303040.12518@fledge.watson.org>, Robert 
> Wats on writes:
>
>> In which case user application threads will need to know their CPU [...]
>
> Didn't jemalloc solve that problem once already ?

I think jemalloc implements thread-affinity for arenas rather than 
CPU-affinity in the strict sense, but I may misread.

Robert N M Watson
Computer Laboratory
University of Cambridge