From owner-freebsd-smp@FreeBSD.ORG Tue Oct 19 16:09:15 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 329F416A4CE for ; Tue, 19 Oct 2004 16:09:15 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB33843D41 for ; Tue, 19 Oct 2004 16:09:14 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by mproxy.gmail.com with SMTP id 74so341087rnk for ; Tue, 19 Oct 2004 09:09:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=q2rMBz4LQIsjU/h22lccggclTSYNH4ilzJ3xhZ3uJD+47WhxMQVm2+cnQ15NY0TrpsVE9FBfojW//DaHPVpO0fZf3pUgQ5snAmVdv3EsdlcGrCgWXpZVVInwo1HtKiUuhnOnBCt6LmYvw0E4yAMLoTkmr9oQyXax1ocI8f4qaUU Received: by 10.38.152.46 with SMTP id z46mr90790rnd; Tue, 19 Oct 2004 09:09:14 -0700 (PDT) Received: by 10.38.13.37 with HTTP; Tue, 19 Oct 2004 09:09:14 -0700 (PDT) Message-ID: <84dead7204101909093c3a6f27@mail.gmail.com> Date: Tue, 19 Oct 2004 21:39:14 +0530 From: Joseph Koshy To: John Baldwin In-Reply-To: <200410141441.56479.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <84dead7204101320022bd6602e@mail.gmail.com> <200410141441.56479.jhb@FreeBSD.org> cc: freebsd-smp@freebsd.org Subject: Re: Moving a kthread between CPUs? X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 16:09:15 -0000 > In 5.x there's a sched_bind() interface that can be used to pin a thread to an > arbitrary CPU. sched_bind() could work. Thanks. A quick grep didn't reveal any uses of sched_{bind,unbind} inside the kernel though ...