From: Robert Love <rml@tech9.net>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: Ryan Cumming <bodnar42@phalynx.dhs.org>,
linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [patch] sched_[set|get]_affinity() syscall, 2.4.15-pre9
Date: 22 Nov 2001 20:16:45 -0500 [thread overview]
Message-ID: <1006478207.1632.16.camel@icbm> (raw)
In-Reply-To: <20011122181125.S1308@lynx.no>
In-Reply-To: <Pine.LNX.4.33.0111220951240.2446-300000@localhost.localdomain> <1006472754.1336.0.camel@icbm> <E16744i-0004zQ-00@localhost> <1006476685.1331.9.camel@icbm> <20011122181125.S1308@lynx.no>
On Thu, 2001-11-22 at 20:11, Andreas Dilger wrote:
> Rather use something else, like CAP_SYS_NICE. It ties in with the idea
> of scheduling, and doesn't further abuse the CAP_SYS_ADMIN capability.
> CAP_SYS_ADMIN, while it has a good name, has become the catch-all of
> capabilities, and if you have it, it is nearly the keys to the kingdom,
> just like root.
Ah, forgot about CAP_SYS_NICE ... indeed, a better idea. I suppose if
people want it a CAP_SYS_CPU_AFFINITY could do, but this is a simple and
rare enough task that we are better off sticking it under something
else.
Robert Love
next prev parent reply other threads:[~2001-11-23 1:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 8:59 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 [this message]
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 ` a nohup-like interface to cpu affinity Linux maillist account
2001-11-27 6:50 ` 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
[not found] <1006832357.1385.3.camel@icbm.suse.lists.linux.kernel>
[not found] ` <5.0.2.1.2.20011127020817.009ed3d0@pop.mindspring.com.suse.lists.linux.kernel>
2001-11-27 7:32 ` [patch] sched_[set|get]_affinity() syscall, 2.4.15-pre9 Andi Kleen
[not found] ` <5.0.2.1.2.20011127020817.009ed3d0@pop.mindspring.com.suse.lists.linux.kerne l>
2001-11-27 21:01 ` Robert Love
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=1006478207.1632.16.camel@icbm \
--to=rml@tech9.net \
--cc=adilger@turbolabs.com \
--cc=bodnar42@phalynx.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome