Re: Paging file

[James Rich <james@xxxxxxxxxxx>]

On Tue, 29 Oct 2002, Dennis Lovelady wrote:

> Huh?

As I said, I don't know for sure - I'm just saying what seems apparent
based on the discussion so far.

> And this is circumvented on other systems?

Yes.  On my linux box memory is paged out to a partition of disk reserved
specifically for it (a swap partition).  So swapping out/in should go
relatively fast as compared to a random read/write.

> Anyway, I believe there's a flaw in your thinking.  If the data needs to be
> rewritten, there's no guarantee that it'll go back to "the same place" on
> the disk.  In fact, if I understand it correctly (and I thought I did), it
> likely won't go back to the same spot.  If it hasn't changed, it won't be
> rewritten.  If it has changed, it's subject to standard writing rules,
> again as I understand it.

My thinking may well be flawed - I don't claim any inside information on
this topic (I know a lot more about linux memory systems than AS/400
memory systems).

The question really boils down to: does the AS/400 swap?  My boss thinks
he may have heard that it does.  One post said that all objects have a
single address, whether on disk or in main memory.  If an object only has
one address, can there be more than one copy of that object?  Can an
object exist both on disk and in memory?  If so, then to which copy does
the address point?  If there can only be one copy of an object, where does
that object go when memory pressure is high?  If the AS/400 swaps, which
on disk copy of an object is pointed to?  If an object in memory is
changed, but the user does not want to write those changes permanently,
and memory pressure is high so that main memory cannot hold the changed
objects, where do those changes go?

Now clearly a copy of objects is made.  When some program object is loaded
of copy of it is made (with its own unique address) and loaded into
memory.  So when memory pressure is high, where do these objects go on
disk?  Is there a swap file/partition?

James Rich