From: Douglas McNaught <doug@mcnaught.org>
To: "Brian D. McGrew" <brian@visionpro.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Binding a thread (or specific process) to a designated CPU
Date: Mon, 22 Aug 2005 18:25:05 -0400 [thread overview]
Message-ID: <m27jed1uf2.fsf@Douglas-McNaughts-Powerbook.local> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA096FF8B@chicken.machinevisionproducts.com> (Brian D. McGrew's message of "Mon, 22 Aug 2005 14:56:47 -0700")
"Brian D. McGrew" <brian@visionpro.com> writes:
> Good morning,
>
> Using FC3 or FC4 with the 2.6.9 or later kernel, we're looking for a way
> to bind a thread (or an entire process) to a designated CPU. We're
> using dual processor systems as well as P4 with HT and Xeons so all of
> our boxes either have two CPU's or 'appear' to have two.
>
> I want to be able, in my C++ code to designate a specific thread to a
> specific processor. I've heard rumors that with the 2.6 kernel this is
> now possible???
Look into sched_setaffinity() and friends.
-Doug
prev parent reply other threads:[~2005-08-22 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 21:56 Binding a thread (or specific process) to a designated CPU Brian D. McGrew
2005-08-22 22:05 ` Jesper Juhl
2005-08-22 22:07 ` Tomasz Torcz
2005-08-22 22:25 ` Douglas McNaught [this message]
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=m27jed1uf2.fsf@Douglas-McNaughts-Powerbook.local \
--to=doug@mcnaught.org \
--cc=brian@visionpro.com \
--cc=linux-kernel@vger.kernel.org \
/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