From: Tim Hockin <thockin@isunix.it.ilstu.edu>
To: rusty@rustcorp.com.au (Rusty Russell)
Cc: npollitt@engr.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Process pinning
Date: Tue, 17 Apr 2001 11:17:26 -0500 (CDT) [thread overview]
Message-ID: <200104171617.LAA06660@isunix.it.ilstu.edu> (raw)
In-Reply-To: <m14nIRX-001RovC@mozart> from "Rusty Russell" at Apr 11, 2001 09:05:47 PM
> disallowed CPU on which it is already running. And even a non-RT
> process will stick on its disallowed CPU as long as nothing else runs
> there.
are we going to keep the cpus_allowed API? If we want the (IMHO) more
flexible sysmp() API - I'll finish the 2.4 port. If we are going to keep
cpus_allowed - I'll just abandon pset and sysmp.
Personally, I like sysmp() and the pset tools better, perhaps with a /proc
extension to it.
next prev parent reply other threads:[~2001-04-17 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 0:08 Nick Pollitt
2001-04-11 11:05 ` Rusty Russell
2001-04-17 16:17 ` Tim Hockin [this message]
2001-04-17 19:25 ` Andrew Morton
2001-04-18 1:24 ` Albert D. Cahalan
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=200104171617.LAA06660@isunix.it.ilstu.edu \
--to=thockin@isunix.it.ilstu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=npollitt@engr.sgi.com \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®