From owner-freebsd-hackers@FreeBSD.ORG Fri May 4 17:05:08 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7254B106566C; Fri, 4 May 2012 17:05:08 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id BF3028FC0A; Fri, 4 May 2012 17:05:07 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q44H55oM009979; Fri, 4 May 2012 19:05:05 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q44H55Is009976; Fri, 4 May 2012 19:05:05 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Fri, 4 May 2012 19:05:05 +0200 (CEST) From: Wojciech Puchar To: Navdeep Parhar In-Reply-To: <4FA1A421.6020601@FreeBSD.org> Message-ID: References: <4FA1A421.6020601@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Fri, 04 May 2012 19:05:06 +0200 (CEST) Cc: freebsd-hackers@freebsd.org Subject: Re: CPU selection for ithreads on 8.3 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: Fri, 04 May 2012 17:05:08 -0000 > cxgbc0} > 12 root -68 - 0K 816K WAIT 7 0:31 0.00% intr{irq280: > cxgbc0} > > Back in the day there used to be code in cxgb to bind different > interrupts to different CPUs but it was removed because the kernel > distributed them across CPUs anyway. So what changed? This appears 8.3 > specific. I don't see it on head and I don't have a 9 system readily maybe stupid question but isn't it better to execute same fragment of code repetitively on same CPU core and don't mess with cache trashing? Of course as long as one core can cope with it.