× 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.


  • Subject: Re: why the 16meg space size limit?
  • From: "Steve Richter" <srichter@xxxxxxxxxxxxx>
  • Date: Mon, 21 May 2001 20:15:46 -0400


>So I am back to my question - what is so special about *USRSPC object that
>you want it to be larger than 16MB ?


alexei,

another example:

the win32 api provides memory mapped files. a windows pgm calls two api's:
CreateFileMapping and MapViewOfFile.  The end result is a 32 bit ptr into a
flat file that can be shared between processes on the system. It is the same
as a space.

The pgmr can move the ptr anywhere within the memory mapped space. The range
of movement is the 32 bit addr limit:  2 gig?.  Pgm variables based on the
ptr can be copied to. This will copy data to the shared memory mapped file
making it available to other processes on the system.

Does linux have this capability?  If it does, how does the iseries implement
this functionality when linux is run on the iseries?

If it does not, what happens when mr torvalds decides to implement it?  Will
linux no longer be able to run on the iseries?



+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.