From owner-freebsd-current@FreeBSD.ORG  Wed Feb 19 19:40:45 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 8B5C2C28;
 Wed, 19 Feb 2014 19:40:45 +0000 (UTC)
Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com
 [IPv6:2a00:1450:4013:c00::22b])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 96B881BE6;
 Wed, 19 Feb 2014 19:40:44 +0000 (UTC)
Received: by mail-ee0-f43.google.com with SMTP id e51so340686eek.30
 for <multiple recipients>; Wed, 19 Feb 2014 11:40:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject
 :content-type:content-transfer-encoding;
 bh=AJWRW5BvtIktqLdiSbIGQr6fS9n54lzMsUVK+6xN5Zc=;
 b=J2Aj/ogk3gD7gbHvR8ldQBLA6TVvbaVn+d9LyCcbIu3FVL+auq2f6/FVA5dwx2GqgR
 m+vodjW8gsxFTwOm+zKNlPmuNQkBUrD/1RMNRgm1ZvT27o+muX763UgD7SHw6oEVZ/TS
 azGZMjDPz8Icn5Vk17OHuwbId3nmObpcnqm5d284aEYzd4cjNZ7WpfmUVrG4hiIXxkwa
 43RXHmUDxd0tFGP/ffrspP6fZGLE+mwI7GPOlUgiCTsD2FyrJIxSyReMZsger19Tp4id
 S8SB4l/T4YpdNYiKiNy0xuEEM53QmJD2DruwSpo4SvqymkhXteMXZtbKC0s52pDXlFM2
 vA3g==
X-Received: by 10.14.149.131 with SMTP id x3mr41808707eej.7.1392838842978;
 Wed, 19 Feb 2014 11:40:42 -0800 (PST)
Received: from mavbook.mavhome.dp.ua ([134.249.139.101])
 by mx.google.com with ESMTPSA id f45sm4375551eeg.5.2014.02.19.11.40.40
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 19 Feb 2014 11:40:41 -0800 (PST)
Sender: Alexander Motin <mavbsd@gmail.com>
Message-ID: <530508B7.7060102@FreeBSD.org>
Date: Wed, 19 Feb 2014 21:40:39 +0200
From: Alexander Motin <mav@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Adrian Chadd <adrian@freebsd.org>
Subject: Re: [rfc] bind per-cpu timeout threads to each CPU
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jeffrey Faden <jeffreyatw@gmail.com>,
 freebsd-current <freebsd-current@freebsd.org>,
 "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Wed, 19 Feb 2014 19:40:45 -0000

Hi.

Clock interrupt threads, same as other ones are only softly bound to 
specific CPUs by scheduler preferring to run them on CPUs where they are 
scheduled. So far that was enough to balance load, but allowed threads 
to migrate, if needed. Is it too flexible for some use case?

-- 
Alexander Motin