Path: utzoo!utgpu!cunews!bnrgate!bigsur!bnr-rsc!nmerh53!hounsell From: hounsell@nmerh53.BNR.CA (Rob Hounsell) Newsgroups: comp.sys.hp Subject: Demand-loaded vs. Shared binaries Keywords: shared demand Message-ID: <4670@bnr-rsc.UUCP> Date: 21 Jun 91 15:34:03 GMT Sender: news@bnr-rsc.UUCP Reply-To: uunet!chekov!hounsell Organization: Northern Telecom Canada Lines: 39 Folks, We are in the middle of a debate about the exact definition of demand-loaded versus shared binaries on our HP-UX 9000/300 and 9000/800 computers. Looking at the manuals on Laserrom, it states that only the HP300 series support demand-loaded code, and that the series 800 (HP-PA) does not. Both models support shared (and non-shared?) code. This brings up several questions, which I hope the gurus at HP can answer. The Response Center was of some help... 1. If the 800s don't support demand-loaded paging, why does chatr allow you to change the attribute to demand-loaded? 2. If the monitor program is run on the 800s, why does it show paging stats in the virtual memory screen, if it doesn't support demand-loading? Does it still use pages to swap in the entire shared code? 3. Can a binary be BOTH demand-loaded and shared? Does setting the demand-load flag prevent the code from being shared? Conversely, does setting the shared flag imply it is demand-loaded as well??? 4. What is the result if you set 800 code to be demand-loaded? What does the loader do then? Based on looking at our machines, it doesn't seem possible that they can run without doing some kind of paging instead of swapping. Can anyone clear this up?? Thanks in advance, Rob +-----------------------------------------------------------------------------+ | Rob Hounsell UUNET: ...!chekov!hounsell | | NT Product Support Technology BNR WAN: hounsell@nmerh53 | | PHONE: (613) 765-2904 | | ESN: 395-2904 | +-----------------------------------------------------------------------------+