From: Jon Masters <jonmasters@gmail.com>
To: Ankit Jain <ankitjain1580@yahoo.com>
Cc: linux <linux-kernel@vger.kernel.org>
Subject: Re: processor affinity
Date: Tue, 28 Sep 2004 14:47:42 +0100 [thread overview]
Message-ID: <35fb2e5904092806477358b9b3@mail.gmail.com> (raw)
In-Reply-To: <20040928122517.9741.qmail@web52907.mail.yahoo.com>
On Tue, 28 Sep 2004 13:25:17 +0100 (BST), Ankit Jain
<ankitjain1580@yahoo.com> wrote:
> what is meant by processor affinity?
Affinity means that a process has an affinity for a particular subset
of the available CPUs within a particular system - it wishes to run
only on these processors. Linux supports hard processor affinity and
process migration to enforce such demands which get be made using the
POSIX sched_[set|get]param calls.
Robert Love has written an excellent book entitled Linux Kernel
Development, it's not expensive and very worthwhile. Chapter 3 is
entitled Scheduling and it explains process affinity as well as
process migration and the concept of migration threads as used within
the Linux kernel to enforce policy in the implmentation.
I suggest also that you consider joining the Kernel Newbies mailing
list, newly revived and now with working signup page over at
http://www.kernelnewbies.org/
Jon.
next prev parent reply other threads:[~2004-09-28 13:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 12:25 processor affinity Ankit Jain
2004-09-28 13:39 ` Toon van der Pas
2004-09-28 13:47 ` Jon Masters [this message]
2004-09-28 13:55 ` Neil Horman
2004-09-28 14:04 ` Jeff V. Merkey
2004-09-28 15:58 ` Robert Love
2004-09-28 16:02 ` Jeff V. Merkey
2004-09-28 21:51 ` Alan Cox
2004-09-29 16:56 ` Jeff V. Merkey
2004-09-29 17:45 ` Christoph Hellwig
2004-09-29 19:24 ` Jeff V. Merkey
2004-09-29 20:08 ` Jon Masters
2004-09-29 19:43 ` Jeff V. Merkey
2004-09-29 20:28 ` Jon Masters
2004-09-29 20:03 ` Jeff V. Merkey
2004-09-30 2:39 ` Nick Piggin
[not found] ` <20040930124708.GA2520@galt.devicelogics.com>
2004-10-01 3:09 ` Nick Piggin
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=35fb2e5904092806477358b9b3@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=ankitjain1580@yahoo.com \
--cc=jonathan@jonmasters.org \
--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