linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Shaheed R. Haque" <srhaque@iee.org>, linux-kernel@vger.kernel.org
Cc: thockin@isunix.it.ilstu.edu
Subject: Re: Re: Processor sets (pset) for linux kernel 2.5/2.6?
Date: Sat, 12 Apr 2003 20:52:11 -0700	[thread overview]
Message-ID: <241480000.1050205930@[10.10.2.4]> (raw)
In-Reply-To: <1050177383.3e986f67b7f68@netmail.pipex.net>

> Hmmm, AFAICS, sched_getaffinity() and sched_setaffinity() 
> allow the calling process to be bound to the nominated CPU(s), but that is not 
> the same as giving them exclusive access, is it? In other words, other 
> processes which have no particualr affinity needs can presumably still be 
> scheduled to run on the same processor. 
> 
> I am looking for something more akin to the patch I referred to...or did I miss 
> something in the effect of set_cpus_allowed()?

The NUMA scheduler work can trivially be converted into arbitrary
scheduler pools - they are not designed for dynamic modification
at the moment, but could be without too much effort I think.

Around 2.5.59 or so I posted a patch to rename them to pools, though
we had a few other things to sort out at the time. I might revive it
at some point - it's pretty simple.

M.


  parent reply	other threads:[~2003-04-13  3:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 11:20 Processor sets (pset) for linux kernel 2.5/2.6? Shaheed R. Haque
2003-04-12 12:11 ` Dave Jones
2003-04-12 12:24 ` Antonio Vargas
2003-04-12 14:54   ` Martin J. Bligh
2003-04-12 18:23   ` Robert Love
2003-04-12 19:56 ` Shaheed R. Haque
2003-04-12 20:02   ` Robert Love
2003-04-13  8:30     ` Shaheed R. Haque
2003-04-13 14:28       ` Robert Love
2003-05-13 11:49         ` 2.6 must-fix list, v2 Shaheed R. Haque
2003-05-13 20:02           ` Andrew Morton
2003-05-13 22:46             ` Shaheed R. Haque
2003-05-14  2:42               ` Steven Cole
2003-05-14 11:49                 ` Shaheed R. Haque
2003-05-14 13:08                   ` Steven Cole
2003-05-13 22:49             ` Shaheed R. Haque
2003-05-14 11:02               ` Felipe Alfaro Solana
2003-05-14 15:59                 ` Robert Love
2003-05-14 16:04                   ` Robert Love
2003-05-14 21:01                   ` shaheed
2003-05-14 21:15                     ` Robert Love
2003-05-15  9:19                       ` Shaheed R. Haque
2003-05-15 15:32                         ` Robert Love
2003-05-15 20:07                           ` shaheed
2003-05-15 20:20                             ` Robert Love
2003-05-15 20:24                             ` Robert Love
2003-05-15 21:30                               ` shaheed
2003-04-13  3:52   ` Martin J. Bligh [this message]
2003-07-15 11:39   ` [HOWTO] Emulate processor sets (pset) for linux kernel 2.5/2.6 \"shaheed r. haque\"
2003-04-14 22:40 ` [RFC] patch to allow CPUs to be reserved to callers of sys_setaffinity [was Processor sets (pset) for linux kernel 2.5/2.6?] shaheed
2003-05-01 20:19 ` Working .config for a Dell 2650 for 2.5.6x? (was Re: Processor sets (pset) for linux kernel 2.5/2.6?) shaheed

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='241480000.1050205930@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srhaque@iee.org \
    --cc=thockin@isunix.it.ilstu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).