From: Hugues Evrard <h.evrard@imperial.ac.uk>
To: 9fans@9fans.net
Cc: Dan Iorga <iorgadan@gmail.com>
Subject: [9fans] Multicore support ARM RaspberryPi
Date: Fri, 21 Jul 2017 10:04:24 +0100 [thread overview]
Message-ID: <97227eaa-e846-b8c6-0f66-e0751becebe3@imperial.ac.uk> (raw)
Hi all,
Does (any flavour of) plan9 / inferno make use of several cores on
(any flavour of) ARM?
We are investigating how a program can create interference (e.g. slow
down) with one running on different a different core in the context of
embedded, real-time systems. It turns out that most real-time OSes have
poor support of multicore, but the plan9 state of affairs is not clear
to us.
I guess plan9 on x86 do support multicore, but is it the case on ARM? In
particular, on the raspberry-pi 3?
Thanks, and if possible keep Dan (CC'ed) in the loop.
Hugues
next reply other threads:[~2017-07-21 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 9:04 Hugues Evrard [this message]
2017-07-21 9:23 ` David du Colombier
2017-07-21 9:56 ` Hugues Evrard
2017-07-21 9:47 cinap_lenrek
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=97227eaa-e846-b8c6-0f66-e0751becebe3@imperial.ac.uk \
--to=h.evrard@imperial.ac.uk \
--cc=9fans@9fans.net \
--cc=iorgadan@gmail.com \
/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).