Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sdcsvax.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!whuxl!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!sdcsvax!jww
From: jww@sdcsvax.UUCP (Joel West)
Newsgroups: net.arch
Subject: Re: Page size and the meaning of life
Message-ID: <1156@sdcsvax.UUCP>
Date: Thu, 24-Oct-85 00:47:31 EST
Article-I.D.: sdcsvax.1156
Posted: Thu Oct 24 00:47:31 1985
Date-Received: Wed, 30-Oct-85 03:48:20 EST
References: <926@decwrl.UUCP>
Organization: CACI, Inc - Federal, La Jolla
Lines: 14
Summary: VMS clusters

In article <926@decwrl.UUCP>, waters@oracle.DEC (Greg Waters, 225-4986, HLO2-1/J12) writes:
> 2.  I agree, page faulting is inefficient with 512 byte pages.  That's why
>     a VAX OS shouldn't fault 512 byte pages.  The size of a page fault can
>     be tuned in software to any multiple of 512 that you like.

VAX/VMS has such a parameter, clustersize.  It appears to be typically
11 pages.  If VMS is using 11, you'd better hope your program
also clusters at 11, or you get some really nasty fragmentation/page
fault performance hassles.


	Joel West	CACI, Inc. - Federal (c/o UC San Diego)
	{ucbvax,decvax,ihnp4}!sdcsvax!jww
	jww@SDCSVAX.ARPA