From: philw@plan9.bell-labs.com philw@plan9.bell-labs.com
Subject: General questions...
Date: Mon, 19 Aug 1996 19:30:02 -0400 [thread overview]
Message-ID: <19960819233002.DJCIk23om2dSSWoZgwuoNa5dp268RwxZu74WvEa5C50@z> (raw)
>adopt the strategy of power/mmu.c and chm/mmu.c: they use a stunningly elegant
>distributed garbage collection algorithm (and very little code)
>to manage a collection of virtual contexts across the TLBs of a multiprocessor.
thank you.
However, there is an additional problem. The 20's have virtual caches
so you also have to deal with page coloring. I faced the problem for
the SGI challenge XL and that was really the start of Brazil.
phil.
next reply other threads:[~1996-08-19 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-19 23:30 philw [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-08-20 14:42 forsyth
1996-08-20 6:57 Nigel
1996-08-19 22:51 forsyth
1996-08-19 20:47 Photon
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=19960819233002.DJCIk23om2dSSWoZgwuoNa5dp268RwxZu74WvEa5C50@z \
--to=philw@plan9.bell-labs.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).