9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 and multicores/parallelism/concurrency?
Date: Thu, 17 Jul 2008 05:26:19 -0700	[thread overview]
Message-ID: <1216297579.4327.85.camel@goose.sun.com> (raw)
In-Reply-To: <f67d430bcb61387b1a6a1084ad0b6e00@9srv.net>

On Mon, 2008-07-14 at 18:12 -0400, a@9srv.net wrote:
> // Not just inexpensive, but also better aligned with how
> // they use compute resources (virtual vs. physical threads)
> // and memory resources.
>
> Hrm. I know about the memory/cache issues, but it sounds
> like there's more on the CPU side I don't know much about.
> Is there more here beyond the memory question and
> prediction/pipelining?

With, what is called CMT, we now have the following hierarchy
of compute resources:
  -> physical CPU
      -> cores
          -> virtual threads
and the following set (I can't quite call it a hierarchy) of memory
resources:
  physical RAM attached to a particular CPU's memory controller
  L3/L2 cache
  L1 cache
These two set of resources can be "attached" to each other in a number
of different ways (e.g. L1 could be the only per-core cache or L2
could also be per-core, etc.) and the job of a scheduler is to figure
out the best mapping of tasks to compute resources based on
alignment constraints. Paul had a nice post on these constraints
earlier. Here's an old post from Ingo outlining what is NOT free
with HyperThreading:
   http://lwn.net/Articles/8553/

> // Speaking of which -- is SPARC port of Plan9 still alive?
>
> Not really. There's a partially-working sparc64 port out there
> which ran on the Ultra 1 (I think), but it's neither been kept up
> to date nor made to run on anything beyond that. A few folks
> (including myself) have poked at it a bit with varying results,
> none of which were particularly good.
>
> Something on Batoka would provide better motivation than my
> old Ultra 5, though!

I don't think I can help much with that, but if I ever see a
homeless Batoka in the hallway it'll be FedExed to you in
no time ;-)

Thanks,
Roman.




  reply	other threads:[~2008-07-17 12:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14  8:45 ssecorp
2008-07-14  9:08 ` sqweek
2008-07-14 16:17   ` Iruata Souza
2008-07-14 16:31   ` Roman V. Shaposhnik
2008-07-14 10:15 ` a
2008-07-14 15:32 ` David Leimbach
2008-07-14 16:00   ` erik quanstrom
2008-07-14 16:29 ` Roman V. Shaposhnik
2008-07-14 20:08   ` a
2008-07-14 20:39     ` Roman V. Shaposhnik
2008-07-14 22:12       ` a
2008-07-17 12:26         ` Roman V. Shaposhnik [this message]
2008-07-17 12:40           ` erik quanstrom
2008-07-17 13:00             ` ron minnich
2008-07-14 20:43     ` Charles Forsyth
2008-07-14 16:35 erik quanstrom
     [not found] <f1209aefaab5eece7465c3d0df545ddd@quanstro.net>
2008-07-14 20:33 ` Roman V. Shaposhnik
2008-07-15  1:37   ` Joel C. Salomon
2008-07-15  8:01   ` Bakul Shah
2008-07-15 17:50     ` Paul Lalonde
2008-07-17 19:29       ` Bakul Shah
2008-07-18  3:31         ` Paul Lalonde

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=1216297579.4327.85.camel@goose.sun.com \
    --to=rvs@sun.com \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).