public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Zoltan.Menyhart@bull.net
Cc: drepper@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: NUMA API - wish list
Date: Mon, 3 May 2004 10:57:35 -0700	[thread overview]
Message-ID: <20040503105735.39bee800.pj@sgi.com> (raw)
In-Reply-To: <40963FAB.DF49BC3E@nospam.org>

> The operating systems should provide for abstractions of the actual ...

True ... so long as you don't confuse "operating system" with "kernel".

Most of what you describe can and should be in user space, as what I
call "system software", constructed of libraries, daemons, utilities
and specific language support.

Having the kernel support the abstraction of "file", to hide details of
sectors, channels and devices has been a great success.  But the kernel
doesn't need to support every such abstraction, such as in this case
"abstract computers" with certain amounts of compute, memory and i/o
resources.

Rather the kernel only needs to provide the essential primitives, such
as cpu and memory placement, jobs (as related set of tasks), and access
to primitive topology and hardware attributes.

(Your spam encoded from address "Zoltan.Menyhart_AT_bull.net@nospam.org"
is a minor annoyance ...).

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373

  reply	other threads:[~2004-05-03 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30  7:35 NUMA API Ulrich Drepper
2004-04-30  8:30 ` William Lee Irwin III
2004-05-03 18:37   ` Ulrich Drepper
2004-05-04 10:01     ` Christoph Hellwig
2004-04-30  8:49 ` Paul Jackson
2004-04-30  9:50   ` William Lee Irwin III
2004-05-03 12:48 ` NUMA API - wish list Zoltan Menyhart
2004-05-03 17:57   ` Paul Jackson [this message]
     [not found] <1QAMU-4gf-15@gated-at.bofh.it>
     [not found] ` <1RLdk-29R-11@gated-at.bofh.it>
2004-05-03 13:17   ` Andi Kleen

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=20040503105735.39bee800.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Zoltan.Menyhart@bull.net \
    --cc=drepper@redhat.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