<?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: malloc internals in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/malloc-internals/m-p/3047590#M812892</link>
    <description>The malloc internals probably won't solve any programming problems. If you are trying to malloc large amounts of memory and are getting errno 12 (ENOMEM), most likely you are compiling a 32bit program and are not aware of the addressing limitations of these programs. If this is the case, start with the kernel parameter: maxdsiz which prevents any 32bit program from getting more than 64megs (the default value) of RAM. &lt;BR /&gt;&lt;BR /&gt;You can set maxdsiz to about 2Gb but then you'll run into another limit at about 950 megs. Your program must be recompiled or relinked with -Wl -N options so both quadrant 2 and most of quadrant 1 can be used for malloc calls. In that case, you'll gain access to almost 1750 megs in a malloc call.&lt;BR /&gt;&lt;BR /&gt;Beyond Q1+Q2 usage, you can use the +q3p and +q4p options but this depends on the opsystem version (11.0 with patches or 11i). Read the mem_mgt *and* proc_mgmt white papers in /usr/share/doc. They are missing in 11i so download them from &lt;A href="http://docs.hp.com" target="_blank"&gt;http://docs.hp.com&lt;/A&gt;</description>
    <pubDate>Wed, 13 Aug 2003 01:12:32 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2003-08-13T01:12:32Z</dc:date>
    <item>
      <title>malloc internals</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/malloc-internals/m-p/3047588#M812890</link>
      <description>Hi, &lt;BR /&gt;I was wondering if there is any public information about the internals of the malloc() function (and the rest of it's family) that is used on hp-ux (&amp;gt; 8.x).&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Aug 2003 23:22:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/malloc-internals/m-p/3047588#M812890</guid>
      <dc:creator>ilja_1</dc:creator>
      <dc:date>2003-08-12T23:22:55Z</dc:date>
    </item>
    <item>
      <title>Re: malloc internals</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/malloc-internals/m-p/3047589#M812891</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;To ask for the internals of a routine like this is like asking for the source, which HP don't disclose and no (sensible) HP employee would give. Look at the linux source for a general idea:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.linux.org/" target="_blank"&gt;http://www.linux.org/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you have any further questions, please let me know and I'll do my best to answer them.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;James.</description>
      <pubDate>Wed, 13 Aug 2003 00:48:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/malloc-internals/m-p/3047589#M812891</guid>
      <dc:creator>James Murtagh</dc:creator>
      <dc:date>2003-08-13T00:48:04Z</dc:date>
    </item>
    <item>
      <title>Re: malloc internals</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/malloc-internals/m-p/3047590#M812892</link>
      <description>The malloc internals probably won't solve any programming problems. If you are trying to malloc large amounts of memory and are getting errno 12 (ENOMEM), most likely you are compiling a 32bit program and are not aware of the addressing limitations of these programs. If this is the case, start with the kernel parameter: maxdsiz which prevents any 32bit program from getting more than 64megs (the default value) of RAM. &lt;BR /&gt;&lt;BR /&gt;You can set maxdsiz to about 2Gb but then you'll run into another limit at about 950 megs. Your program must be recompiled or relinked with -Wl -N options so both quadrant 2 and most of quadrant 1 can be used for malloc calls. In that case, you'll gain access to almost 1750 megs in a malloc call.&lt;BR /&gt;&lt;BR /&gt;Beyond Q1+Q2 usage, you can use the +q3p and +q4p options but this depends on the opsystem version (11.0 with patches or 11i). Read the mem_mgt *and* proc_mgmt white papers in /usr/share/doc. They are missing in 11i so download them from &lt;A href="http://docs.hp.com" target="_blank"&gt;http://docs.hp.com&lt;/A&gt;</description>
      <pubDate>Wed, 13 Aug 2003 01:12:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/malloc-internals/m-p/3047590#M812892</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-08-13T01:12:32Z</dc:date>
    </item>
  </channel>
</rss>

