public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Joe Korty <l-k@mindspring.com>
Cc: mingo@elte.hu, Ryan Cumming <bodnar42@phalynx.dhs.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sched_[set|get]_affinity() syscall, 2.4.15-pre9
Date: 27 Nov 2001 15:53:04 -0500	[thread overview]
Message-ID: <1006894385.819.2.camel@phantasy> (raw)
In-Reply-To: <5.0.2.1.2.20011127020817.009ed3d0@pop.mindspring.com>
In-Reply-To: <1006832357.1385.3.camel@icbm>  <5.0.2.1.2.20011127020817.009ed3d0@pop.mindspring.com>

On Tue, 2001-11-27 at 02:13, Joe Korty wrote:

> I have not yet seen the patch, but one nice feature that a system call 
> interface could provide is the ability to *atomically* change the cpu
> affinities of sets of processes -- for example, all processes with a
> certain uid or gid.  All that would be required would be for the system
> call to accept a command integer value which would define what the
> argument integer value would mean -- a pid, a gid, or a uid.

Effecting all tasks matching a uid or some other filter is a little
beyond what either patch does.  Note however that both interfaces have
atomicity.

You can open and write to proc from within a program ... very easily, in
fact.

Also, with some sed and grep magic, you can set the affinity of all
tasks via the proc interface pretty easy.  Just a couple lines.

	Robert Love


  reply	other threads:[~2001-11-27 20:52 UTC|newest]

Thread overview: 39+ 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  0:51     ` Robert Love
2001-11-23  1:11       ` Andreas Dilger
2001-11-23  1:16         ` Robert Love
2001-11-23 11:36     ` Ingo Molnar
2001-11-24  2:01       ` Davide Libenzi
2001-11-27  3:39     ` Robert Love
2001-11-27  7:13       ` Joe Korty
2001-11-27 20:53         ` Robert Love [this message]
2001-11-27 21:31           ` Nathan Dabney
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  4:41     ` a nohup-like interface to cpu affinity Linux maillist account
2001-11-27  4:49       ` Robert Love
2001-11-27  6:32       ` Linux maillist account
2001-11-27  6:39         ` Robert Love
2001-11-27  8:42           ` Sean Hunter
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:50       ` a nohup-like interface to cpu affinity Linux maillist account
2001-11-27  8:26       ` Ingo Molnar
2001-11-23 11:02   ` [patch] sched_[set|get]_affinity() syscall, 2.4.15-pre9 Ingo Molnar
     [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   ` Andi Kleen
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=1006894385.819.2.camel@phantasy \
    --to=rml@tech9.net \
    --cc=bodnar42@phalynx.dhs.org \
    --cc=l-k@mindspring.com \
    --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