mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phil Howard <phil-linux-kernel@ipal.net>
To: Joe Korty <l-k@mindspring.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: procfs bloat, syscall bloat [in reference to cpu affinity]
Date: Tue, 27 Nov 2001 08:04:41 -0600	[thread overview]
Message-ID: <20011127080441.A12419@vega.ipal.net> (raw)
In-Reply-To: <1006832357.1385.3.camel@icbm> <5.0.2.1.2.20011127022738.009f14b0@pop.mindspring.com>
In-Reply-To: <5.0.2.1.2.20011127022738.009f14b0@pop.mindspring.com>

On Tue, Nov 27, 2001 at 03:04:27AM -0500, Joe Korty wrote:

| I am not against a proc interface per se, I would like a proc interface, 
| especially for the
| reading of affinity values.  But in my view the system call interface 
| should also exist
| and it should be the dominate way of communicating affinity to processes.

IWSTM that the way you would justify this being a system call would also
suggest working with non-linux kernel developers (both open source as well
as commercial) to determine a mutually agreed syntax/semantic for this
call to further ensure the basis of the universality that ensure it will
be one of those "forever" facilities, and maybe even make it into a future
standard.

You opened the camel's mouth; do you want to check the teeth?

-- 
-----------------------------------------------------------------
| Phil Howard - KA9WGN |   Dallas   | http://linuxhomepage.com/ |
| phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/     |
-----------------------------------------------------------------

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

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=20011127080441.A12419@vega.ipal.net \
    --to=phil-linux-kernel@ipal.net \
    --cc=l-k@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®