<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Bus addressable memory in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567820#M69152</link>
    <description>Wim,&lt;BR /&gt;&lt;BR /&gt;with 128 MB of memory, there should be no problem for the IO adapter (assumimg you also have a Qlogic ISP 1020) to address all of physical memory. If there is no BAP, datastructures (for this adapter) would then be allocated from normal nonpaged pool.&lt;BR /&gt;&lt;BR /&gt;Use SEARCH SYS$SYSTEM:AGEN$FEEDBACK.DAT BAP to see which values of BAP AUTOGEN feedback is suggesting. &lt;BR /&gt;&lt;BR /&gt;You can certainly override the NPAG_BAP_* values to prevent BAP pool from being created in this kind of config.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Wed, 22 Jun 2005 02:40:39 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2005-06-22T02:40:39Z</dc:date>
    <item>
      <title>Bus addressable memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567813#M69145</link>
      <description>Anyone an idea what it is used for ?&lt;BR /&gt;I have 1 node running 8.2 that has allocated zero bytes for it.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 21 Jun 2005 10:09:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567813#M69145</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-06-21T10:09:18Z</dc:date>
    </item>
    <item>
      <title>Re: Bus addressable memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567814#M69146</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;there are certain IO adapters (CIPCA, CIXCD, KFMSB, and Qlogic 1020ISP), that are limited in addressing physical memory beyond 1GB or 4GB. To overcome this restriction, some data structures used by those adapters have to be allocated in BAP pool (Bus Adressable Pool), which will be configured to reside in physical memory at  addresses lower than 1 or 4 GB.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/73final/6017/6017pro_070.html" target="_blank"&gt;http://h71000.www7.hp.com/doc/73final/6017/6017pro_070.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The NPAG_BAP_* parameters control this pool.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Tue, 21 Jun 2005 10:22:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567814#M69146</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-06-21T10:22:16Z</dc:date>
    </item>
    <item>
      <title>Re: Bus addressable memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567815#M69147</link>
      <description>It seems that autogen put the npag_bap_min and max on 0 when it was standalone but still used something. When I clustered the station with 7.3 nothing was used. I now did an autogen and rebooted and it is using 110 K of the maximum of 128 K (which is npag_bap_max).&lt;BR /&gt;&lt;BR /&gt;Wim&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Jun 2005 10:52:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567815#M69147</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-06-21T10:52:19Z</dc:date>
    </item>
    <item>
      <title>Re: Bus addressable memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567816#M69148</link>
      <description>because non-paged pool can reach to addresses that some adapaters can not handle (as Volker mentioned) then a seperate pool is created (BAP) which is always  placed where it can be accessed by any adaptor. It gets created as a seperate pool by AUTOGEN setting the system paramters to non-zero values if your non-paged pool becomes big enough so that some of it may be in parts of the address space that some adaptors can not access.</description>
      <pubDate>Tue, 21 Jun 2005 11:26:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567816#M69148</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-06-21T11:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: Bus addressable memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567817#M69149</link>
      <description>Ian &amp;amp; Volker,&lt;BR /&gt;&lt;BR /&gt;This concerns an AS500 with 128 MB and 512 MB pagefile. Why does it need those structures ? For the disk of 2 GB ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 21 Jun 2005 15:01:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567817#M69149</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-06-21T15:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: Bus addressable memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567818#M69150</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;I'm seeing similar results on an AlphaServer 1000A V8.2 with 128 MB memory. BAP pool is 128 KB with 17.1 KB used. This system has 2 Qlogic ISP1020 SCSI-2 adapters (see SDA&amp;gt; CLUE CONFIG).&lt;BR /&gt;&lt;BR /&gt;This has nothing to do with disk size or such. Some IO adapters (plugged into PCI or XMI buses) just can't handle 'high' physical memory addresses and as they sometimes need to allocate datastructures from nonpaged pool, the operating system needs to provide bus adressable pool mapped to 'lower' physical addresses.&lt;BR /&gt;&lt;BR /&gt;Use SDA&amp;gt; SHOW POOL/BAP/HEADER to see, which data structures are allocated in BAP pool.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 22 Jun 2005 00:49:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567818#M69150</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-06-22T00:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: Bus addressable memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567819#M69151</link>
      <description>Volker,&lt;BR /&gt;&lt;BR /&gt;OK but what did it do when the usage was zero ? Live without it ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 22 Jun 2005 01:40:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567819#M69151</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-06-22T01:40:49Z</dc:date>
    </item>
    <item>
      <title>Re: Bus addressable memory</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567820#M69152</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;with 128 MB of memory, there should be no problem for the IO adapter (assumimg you also have a Qlogic ISP 1020) to address all of physical memory. If there is no BAP, datastructures (for this adapter) would then be allocated from normal nonpaged pool.&lt;BR /&gt;&lt;BR /&gt;Use SEARCH SYS$SYSTEM:AGEN$FEEDBACK.DAT BAP to see which values of BAP AUTOGEN feedback is suggesting. &lt;BR /&gt;&lt;BR /&gt;You can certainly override the NPAG_BAP_* values to prevent BAP pool from being created in this kind of config.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 22 Jun 2005 02:40:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/bus-addressable-memory/m-p/3567820#M69152</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-06-22T02:40:39Z</dc:date>
    </item>
  </channel>
</rss>

