Path: utzoo!attcan!uunet!cs.utexas.edu!wuarchive!usc!apple!vsi1!frame!ciara!sbs From: sbs@ciara.Frame.COM (Steven Sargent) Newsgroups: comp.arch Subject: Re: Page size and linkers (was: Re: SunMMU history) Message-ID: <9840@frame.UUCP> Date: 23 Jan 91 05:12:19 GMT References: <1991Jan19.133914.23871@bellcore.bellcore.com> <3981@skye.ed.ac.uk> Sender: news@frame.UUCP Reply-To: sbs@ciara.Frame.COM (Steven Sargent) Organization: Frame Technology Corp Lines: 22 In article <3981@skye.ed.ac.uk>, richard@aiai.ed.ac.uk (Richard Tobin) writes: |> In article pcg@cs.aber.ac.uk (Piercarlo Grandi) writes: |> >Incidentally, even a 4KB pagesize is still too large, even if it is |> >barely tolerable. 8KB was simply crazy, for a workstation/time sharing |> >server. |> |> Large page sizes seem likely to interact badly with programs |> containing a large number of small procedures, such as X clients. An |> obvious improvement would be to have the linker order procedures so that |> procedures commonly used together were adjacent, and separate from |> rarely used procedures. |> |> Has this been done in any real systems? |> NeXT's 2.0 linker provides a scheme for ordering procedures. I've used it to separate out startup code from the rest of the program and gotten good results (naturally, the numbers aren't handy.) Special flags to gprof cause it to present output in a form useful to the linker. -- Steven Sargent sbs@frame.com "Frame's phone bill, my opinions."