SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Spots who wrote (3555)11/15/1998 9:47:00 PM
From: Dave Hanson  Read Replies (2) | Respond to of 14778
 
Again, very helpful. I'm sure others agree. Question: given that all real mem is mapped to the pagefile, why does tskmgr indicate that total memory is real mem + swapfile? Just a (misleading) convention? If would be more useful to list available memory as the larger of the pagefile or the physical ram, since that's all it will hold anyway.

Obviously I was misinformed about the allocation of data to the swapfile. Thanks for clearing that up! Apologies to Mrs. Spots too <g>.



To: Spots who wrote (3555)11/15/1998 10:53:00 PM
From: Sean W. Smith  Read Replies (1) | Respond to of 14778
 
Spots,

you are very correct. Many flavors of unix share this attribute. SunOs which was based on BSD behaves the same way. Solaris 2.0 (System V) based actually treat total memory = physical memory + swap space - small overhead. This works very nice although is certainly a more complicated algoritm to impliment in the virtual memory manager.
As there is no direct static mapping of segments as the older more established algorithms...

Sean


HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News