public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linux maillist account <l-k@mindspring.com>
To: Robert Love <rml@tech9.net>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: a nohup-like interface to cpu affinity
Date: Tue, 27 Nov 2001 01:32:19 -0500	[thread overview]
Message-ID: <5.0.2.1.2.20011127011901.009ebd30@pop.mindspring.com> (raw)
In-Reply-To: <1006836589.842.4.camel@phantasy>
In-Reply-To: <5.0.2.1.2.20011126231737.009f0ec0@pop.mindspring.com> <E16744i-0004zQ-00@localhost> <Pine.LNX.4.33.0111220951240.2446-300000@localhost.localdomain> <1006472754.1336.0.camel@icbm> <E16744i-0004zQ-00@localhost> <5.0.2.1.2.20011126231737.009f0ec0@pop.mindspring.com>

At 11:49 PM 11/26/01 -0500, Robert Love wrote:
>I can see the use for this, but you can also just do `echo whatever >
>/proc/123/affinity' once it is running ... not a big deal.


It's isn't quite the same..the biggest difference is races.  The cpuselect(1)
tool would change the affinity mask before the fork & exec of the first 
child.  To
do this by hand via an `echo whatever >/proc/123/affinity' would miss all the
children spun off by 123 before the echo could be executed.  One could write
cpuselect as a shell script I suppose, using within it an echo on 
/proc/self/affinity,
though even as a shell script it would be better to have this tool be part 
of the standard
Linux repetoire that everyone could depend upon as being there in all Linux 
distributions
and having a well known and unchanging syntax and semantics,  rather than 
have it
remain something that each user creates ad-hoc as the need for the tool arises.

Joe


  parent reply	other threads:[~2001-11-27  6:31 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  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
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 [this message]
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

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.20011127011901.009ebd30@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