Re: why the 16meg space size limit? -- MI400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

So, could a teraspace pointer have a diff "k" value and shift the segment value over a byte or two?

KAAAA000 0000SSSS SSSSSS00 0000TTAA

Then use the addr xlate tables or whatever built into the cpu to provide a contiguous looking group of segments? The intel 386 architecture solved the segment problem with paging and addr xlate support built into the cpu. no

====> so, all we need is an Intel/386 to run OS/400 :-)

For all I know that is how they implement a teraspace in the first place.

The problem is that teraspaces are not 1st class objects, hence cannot

be made permanent etc. As with any architechture, once the segments

become too small, it becomes a major pain to circumvent the limits.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.