<?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: why do shared libraries consume shared memory resources? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/why-do-shared-libraries-consume-shared-memory-resources/m-p/2541975#M865620</link>
    <description>It is not that shared libraries consume RAM.  Shared library text areas consume address space.  The 1.75GB limit on shared objects is the amount of address range that can be used for sharing.&lt;BR /&gt;You can actually get more shared memory for specific programs by linking with the -N option and running&lt;BR /&gt;chatr -M a.out&lt;BR /&gt;That makes the data area start in the first quadrant, then gives the second quadrant to shared memory.</description>
    <pubDate>Tue, 19 Jun 2001 16:23:16 GMT</pubDate>
    <dc:creator>Mike Stroyan</dc:creator>
    <dc:date>2001-06-19T16:23:16Z</dc:date>
    <item>
      <title>why do shared libraries consume shared memory resources?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-do-shared-libraries-consume-shared-memory-resources/m-p/2541974#M865619</link>
      <description>Why is it that shared libraries are included in the system's global space(maximum total shared memory + shared&lt;BR /&gt;libraries + shared memory mapped files for the system is 1.75 GB for 32 bit)?  are shared libraries locked in memory?</description>
      <pubDate>Mon, 18 Jun 2001 21:54:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-do-shared-libraries-consume-shared-memory-resources/m-p/2541974#M865619</guid>
      <dc:creator>Byron Myers</dc:creator>
      <dc:date>2001-06-18T21:54:58Z</dc:date>
    </item>
    <item>
      <title>Re: why do shared libraries consume shared memory resources?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-do-shared-libraries-consume-shared-memory-resources/m-p/2541975#M865620</link>
      <description>It is not that shared libraries consume RAM.  Shared library text areas consume address space.  The 1.75GB limit on shared objects is the amount of address range that can be used for sharing.&lt;BR /&gt;You can actually get more shared memory for specific programs by linking with the -N option and running&lt;BR /&gt;chatr -M a.out&lt;BR /&gt;That makes the data area start in the first quadrant, then gives the second quadrant to shared memory.</description>
      <pubDate>Tue, 19 Jun 2001 16:23:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-do-shared-libraries-consume-shared-memory-resources/m-p/2541975#M865620</guid>
      <dc:creator>Mike Stroyan</dc:creator>
      <dc:date>2001-06-19T16:23:16Z</dc:date>
    </item>
    <item>
      <title>Re: why do shared libraries consume shared memory resources?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-do-shared-libraries-consume-shared-memory-resources/m-p/2541976#M865621</link>
      <description>Hi Byron,&lt;BR /&gt;&lt;BR /&gt;Mike has given you the correct answer; this is one of the main reasons you should be looking at 64-bit 11.x unless of course you have legacy applications.</description>
      <pubDate>Tue, 19 Jun 2001 17:12:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-do-shared-libraries-consume-shared-memory-resources/m-p/2541976#M865621</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-06-19T17:12:26Z</dc:date>
    </item>
  </channel>
</rss>

