RE: why the 16meg space size limit?

Don, Steve et al
 Just my $0.02: 
 I appreciated Lief laying out the basic layout of a MI pointer. 
 I must admit, I was (mildly) surprised to see that the "small SID" (segment 
ID) design in the S/38 is still with us.
 As to Steve's question about why 16MB, I'll offer my speculation based on 
having worked in hardware development of the S/38 CPU: at the time, we could 
(with reasonable $$$ tradeoffs) build the hardware and microcode to support 
that structure. (No stones from the guys who know that the real S/38 hardware 
(models 3, 5, and 7) used an offset of 16 bits --- as published in some of the 
very old S/38 CE books and microfiche). 
 Best regards
George Lemen
Strategic Solutions Inc. e-mail: george@strategicsol.com; phone (425) 462-6446
personal: georgelemen@seanet.com; cell phone (206) 419-6225

----------
From:   Don[SMTP:dr2@cssas400.com]
Reply To:       MI400@midrange.com
Sent:   Monday, May 21, 2001 5:05 PM
To:     MI400@midrange.com
Subject:        Re: why the 16meg space size limit?



> 
> I learned what I know of computers by listening to ibm reasons for why the
> s/38 architecture was best. single level store,  pointers with capability,
> seamless migration to 64 bits, etc.  An effectively unlimited limit? ( 1
> gig ) to the size of a space, is in my opinion, a logical and usefull
> extension of this design concept.
> 
> Steve Richter


Steve, et al,

I'm hearing that if IBM had to do it over, they wouldn't do single level
storeage or would do it differently.  Evidently they're being beat up by
some of the unix constructs when it comes to allocation of storeage...

Does anyone have any further enlightenment here 'cuz I'm no eunochs weinie
when it comes to this.....and I'm curious as heck...

Don in DC



+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

application/ms-tnef