From: Dan Cross <crossd@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Thu, 22 Dec 2022 12:33:12 -0500 [thread overview]
Message-ID: <CAEoi9W7yRJB0eXg=VZB-jgSZCjTyhrHhpUiN6dtWko8eM+eOcA@mail.gmail.com> (raw)
In-Reply-To: <20221222172654.965D618C079@mercury.lcs.mit.edu>
On Thu, Dec 22, 2022 at 12:27 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
> > From: Bakul Shah
>
> > There is a further para:
>
> > Reducing external memory fragmentation to zero by utilizing the VAX-
> > 11/780 memory mapping hardware for scatter loading is high on the list
> > of things to do in the second implementation pass.
>
> I'm curious as to exactly what is meant by "external memory"? They must mean
> memory on the Synchronous Backplane Interconnect:
>
> http://gunkies.org/wiki/Synchronous_Backplane_Interconnect
>
> I.e. what most of us would call 'main memory'.
> [snip]
I think you left off a critical word: "fragmentation." I interpreted this to be
about external memory fragmentation a la memory allocators. As in,
https://en.wikipedia.org/wiki/Fragmentation_(computing)#External_fragmentation
Presumably, this would be less of an issue if they were actually making use
of the virtual memory hardware to compose contiguous virtual address spaces
from discontiguous physical memory pages.
- Dan C.
next prev parent reply other threads:[~2022-12-22 17:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 17:26 Noel Chiappa
2022-12-22 17:33 ` Dan Cross [this message]
2022-12-22 20:25 ` Warner Losh
2022-12-22 23:06 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2022-12-20 22:25 Noel Chiappa
2022-12-20 23:18 ` Bakul Shah
2022-12-19 17:38 [TUHS] " Phil Budne
2022-12-19 18:53 ` [TUHS] " segaloco via TUHS
2022-12-19 21:01 ` Clem Cole
2022-12-19 21:19 ` Rob Pike
2022-12-19 22:15 ` segaloco via TUHS
2022-12-20 0:02 ` Brad Spencer
2022-12-20 1:04 ` Adam Thornton
2022-12-20 2:35 ` segaloco via TUHS
2022-12-20 14:25 ` Andrew Hume
2022-12-19 23:02 ` Clem Cole
2022-12-20 1:20 ` Larry Stewart
2022-12-20 1:33 ` Larry McVoy
2022-12-20 1:57 ` George Michaelson
2022-12-20 2:06 ` Dan Cross
2022-12-20 15:04 ` Chet Ramey
2022-12-20 2:12 ` Adam Thornton
2022-12-20 15:29 ` Andy Kosela
2022-12-20 15:35 ` Adam Thornton
2022-12-21 2:43 ` Luther Johnson
2022-12-20 23:18 ` David Arnold
2022-12-20 2:52 ` Bakul Shah
2022-12-20 3:09 ` Larry McVoy
2022-12-20 3:27 ` Bakul Shah
2022-12-20 3:48 ` Warner Losh
2022-12-20 4:21 ` Jonathan Gray
2022-12-19 21:36 ` Marc Donner
2022-12-19 22:52 ` Charles H Sauer (he/him)
2022-12-20 3:11 ` Warner Losh
2022-12-20 8:56 ` arnold
2022-12-20 9:31 ` segaloco via TUHS
2022-12-20 9:39 ` arnold
2022-12-20 9:55 ` Jonathan Gray
2022-12-20 14:27 ` Clem Cole
2022-12-23 1:53 ` Rob Gingell
2022-12-22 19:00 ` Andrew Hume
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='CAEoi9W7yRJB0eXg=VZB-jgSZCjTyhrHhpUiN6dtWko8eM+eOcA@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).