From: kevin.bowling@kev009.com (Kevin Bowling)
Subject: NUMA, Sequent NUMA-Q, etc
Date: Tue, 3 Oct 2017 22:14:16 -0700 [thread overview]
Message-ID: <CAK7dMtACwghFSG5aDz16nMhspbuuWxdR0W1ab3HmeBps+MucSQ@mail.gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
NUMA is something that's been on my mind a lot lately. Partially in
seeding beastie ideas into Larry McVoy's brain.
I asked Paul McKenney for some history on what went down at Sequent
since that's before my time. He sent me this, which I think the group
will enjoy: http://www2.rdrop.com/users/paulmck/techreports/stingcacm3.1999.08.04a.pdf
It looks pretty nice. Not sure anyone's come as close as Irix to
solving and productizing "easy" NUMA but that's the one I have the
most hands on experience with. They can affine, place, migrate, and
even replicate many types of resources including vnodes. I'm actually
surprised all that code seems to have been spiked and it doesn't seem
like either Sequent née IBM nor SGI brought forward any of their
architecture to Linux. Paul did RCU which is a tour de force, but the
Linux topology and MM code looks like the product of sustaining
engineers instead of architectural decree. Maybe the SCO lawsuit
snubbed all of that?
HP has an out of date competitive analysis that's worth a look
http://h20566.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=5060289&docLocale=en_US&docId=emr_na-c02670417.
I don't have enough seat time with Tru64 but maybe they had some good
ideas.
As open source, I do like Illumos' locality groups. I can't make much
sense of Linux on this, too much seems to be in arch/ vs a first class
concept like locality groups.
Regards,
Kevin
reply other threads:[~2017-10-04 5:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAK7dMtACwghFSG5aDz16nMhspbuuWxdR0W1ab3HmeBps+MucSQ@mail.gmail.com \
--to=kevin.bowling@kev009.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).