Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc!tank!eecae!cps3xx!rang
From: rang@cpsin3.cps.msu.edu (Anton Rang)
Newsgroups: comp.unix.wizards
Subject: Re: GNU OS suggestion -- memory "advice"
Message-ID: <3326@cps3xx.UUCP>
Date: 6 Jun 89 22:55:18 GMT
References: <1343@marvin.Solbourne.COM> <3496@orca.WV.TEK.COM>
Sender: usenet@cps3xx.UUCP
Reply-To: rang@cpsin3.cps.msu.edu (Anton Rang)
Organization: Michigan State University, Computer Science Dept.
Lines: 16

In article <3496@orca.WV.TEK.COM> andrew@frip.WV.TEK.COM (Andrew Klossner) writes:
>  [ stuff about row-major vs. column-major order ]
>
>Well, sure; in column-major order (assuming a non-Fortran language),
>the program is stepping to a new page much more often than in row-major
>order.  If a single row is a page or more in size, column-major order
>will touch a new page with every single index iteration.  No amount of
>memory advice to the OS can mitigate the result of this pathological
>behavior.

  How about asking for a LIFO paging strategy on that section of memory?

+---------------------------+------------------------+
| Anton Rang (grad student) | "VMS Forever!"         |
| Michigan State University | rang@cpswh.cps.msu.edu |
+---------------------------+------------------------+