mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linux maillist account <l-k@mindspring.com>
To: Robert Love <rml@tech9.net>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: a nohup-like interface to cpu affinity
Date: Mon, 26 Nov 2001 23:41:58 -0500	[thread overview]
Message-ID: <5.0.2.1.2.20011126231737.009f0ec0@pop.mindspring.com> (raw)
In-Reply-To: <1006832357.1385.3.camel@icbm>
In-Reply-To: <E16744i-0004zQ-00@localhost> <Pine.LNX.4.33.0111220951240.2446-300000@localhost.localdomain> <1006472754.1336.0.camel@icbm> <E16744i-0004zQ-00@localhost>

Robert and Ingo,
A nohup-like interface to the cpu affinity service would be useful.  It 
could work like the
following example:

    $ cpuselect -c 1,3-5 gcc -c module.c

which would restrict this instantiation of gcc and all of its children to 
cpus 1,3,4, and 5.  This
tool can be implemented in a few lines of C, with either /proc or syscall 
as the underlying
implementation.

On another subject -- capabilities -- any process should be able to reduce 
the number of
cpus in its own cpu affinity mask without any special permission.  To add 
cpus to a
reduced mask, or to change the cpu affinity mask of other processes, should 
require
the appropriate capability, be it CAP_SYS_NICE, CAP_SYS_ADMIN, or whatever
is decided.

Joe 


  parent reply	other threads:[~2001-11-27  4:41 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22  8:59 [patch] sched_[set|get]_affinity() syscall, 2.4.15-pre9 Ingo Molnar
2001-11-22 20:22 ` Davide Libenzi
2001-11-22 23:45 ` Robert Love
2001-11-23  0:20   ` Ryan Cumming
2001-11-23  0:36     ` Mark Hahn
2001-11-23 11:46       ` Ingo Molnar
2001-11-24 22:44         ` Davide Libenzi
2001-11-23 11:36     ` Ingo Molnar
2001-11-24  2:01       ` Davide Libenzi
2001-11-23  0:51   ` Robert Love
2001-11-23  1:11     ` Andreas Dilger
2001-11-23  1:16     ` Robert Love
2001-11-23 11:02   ` Ingo Molnar
2001-11-27  3:39   ` Robert Love
2001-11-27  7:13     ` Joe Korty
2001-11-27  8:04     ` procfs bloat, syscall bloat [in reference to cpu affinity] Joe Korty
2001-11-27 11:32       ` Ingo Molnar
2001-11-27 20:56         ` Robert Love
2001-11-27 14:04       ` Phil Howard
2001-11-27 18:05         ` Tim Hockin
2001-11-27  8:40     ` [patch] sched_[set|get]_affinity() syscall, 2.4.15-pre9 Ingo Molnar
2001-11-27 20:53     ` Robert Love
2001-11-27 21:31       ` Nathan Dabney
2001-11-27  4:41   ` Linux maillist account [this message]
2001-11-27  6:50     ` a nohup-like interface to cpu affinity Linux maillist account
2001-11-27  8:26     ` Ingo Molnar
2001-11-27  4:49   ` Robert Love
2001-11-27  6:32   ` Linux maillist account
2001-12-06  1:35     ` Matthew Dobson
2001-12-06  1:37     ` [RFC][PATCH] cpus_allowed/launch_policy patch, 2.4.16 Matthew Dobson
2001-12-06  2:08       ` Davide Libenzi
2001-12-06  2:17         ` Matthew Dobson
2001-12-06  2:39           ` Davide Libenzi
2001-12-06  2:42         ` Robert Love
2001-12-06 22:21           ` Matthew Dobson
2001-11-27  6:39   ` a nohup-like interface to cpu affinity Robert Love
2001-11-27  8:42     ` Sean Hunter

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=5.0.2.1.2.20011126231737.009f0ec0@pop.mindspring.com \
    --to=l-k@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@tech9.net \
    /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®