public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Tigran Aivazian <tigran@veritas.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Bill Davidsen <davidsen@tmr.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Latest microcode data from Intel.
Date: Fri, 10 Sep 2004 09:39:04 -0700	[thread overview]
Message-ID: <20040910093904.R1973@build.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0409101702270.1294-100000@einstein.homenet>; from tigran@veritas.com on Fri, Sep 10, 2004 at 05:04:35PM +0100

* Tigran Aivazian (tigran@veritas.com) wrote:
> sense (as it is impossible under Linux to bind userspace app to a given 
> cpu then there is no "good" sense in which "per cpu" node can be defined).

sched_setaffinity(2) allows you to bind a userspace app to a given cpu.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2004-09-10 16:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 16:32 Latest microcode data from Intel Tigran Aivazian
2004-09-09 21:10 ` DaMouse
2004-09-10 15:39 ` Bill Davidsen
2004-09-10 15:46   ` Tigran Aivazian
2004-09-10 14:54     ` Alan Cox
2004-09-10 16:04       ` Tigran Aivazian
2004-09-10 16:39         ` Chris Wright [this message]
2004-09-11 21:10           ` Tigran Aivazian
2004-09-10 16:14     ` Kurt Wall
2004-09-15 15:31     ` Bill Davidsen
2004-09-15 15:43       ` Tigran Aivazian
2004-09-15 15:52         ` Dave Jones
2004-09-15 16:09           ` Bill Davidsen
2004-09-10 15:47   ` Nathan Bryant
2004-09-10 15:02     ` Alan Cox
2004-09-10 15:53     ` Tigran Aivazian
2004-09-10 16:44       ` Anton Blanchard
2004-09-10 16:53 ` Dominik Karall
  -- strict thread matches above, loose matches on Subject: below --
2004-09-09 22:21 Chris Rankin
2004-09-10 21:07 watermodem

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040910093904.R1973@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@veritas.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox