<?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: maxdsiz_64bit in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496373#M364293</link>
    <description>&amp;gt;John:&lt;BR /&gt;&lt;BR /&gt;maxtsiz: the maximum size of a code/text segment&lt;BR /&gt;&lt;BR /&gt;maxdsiz: the maximum size of the user/private data segment&lt;BR /&gt;&lt;BR /&gt;maxssiz: the maximum size of the user stack segment&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Dennis: This is for PA or Integrity 32 bit. For 64 bit, there are octants and that comes the high order bits.&lt;BR /&gt;&lt;BR /&gt;probably you are right, my notes seem little bit older. do you know any document about this topic recent updated ? &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Sun, 13 Sep 2009 08:59:07 GMT</pubDate>
    <dc:creator>Hakki Aydin Ucar</dc:creator>
    <dc:date>2009-09-13T08:59:07Z</dc:date>
    <item>
      <title>maxdsiz_64bit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496368#M364288</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I have server "ia64 hp superdome server SD64B", &lt;BR /&gt;I received a request from Application team to increase the size to 48GB as equal to physical memory size. My question how i could know the biggest segment size so according to that i can make my decesion?&lt;BR /&gt;&lt;BR /&gt;Regards,</description>
      <pubDate>Sat, 12 Sep 2009 10:12:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496368#M364288</guid>
      <dc:creator>John Ferro</dc:creator>
      <dc:date>2009-09-12T10:12:51Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz_64bit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496369#M364289</link>
      <description>You can increase it to 48 Gb or larger, if you have that much swap.&lt;BR /&gt;&lt;BR /&gt;You won't be running very many other applications if this one is going to use all of that space.</description>
      <pubDate>Sat, 12 Sep 2009 10:55:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496369#M364289</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-09-12T10:55:41Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz_64bit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496370#M364290</link>
      <description>Addition to Dennis said about limits it is critical to increase this value ,peruse following:&lt;BR /&gt;&lt;BR /&gt;The reason we limit these values is to ensure that a single process doesn't consume all the available memory. Remember, a process's view of memory is via its Virtual Address Space. A 64-bit process thinks it has access to 16EB of memory. This is the theoretical limit of a 64-bit operating system. HP-UX currently uses only 44 of the 64 bits. This limits the size of the entire address space to only 16TB. This should be enough for the foreseeable future. The fact that HP-UX uses the memory partitioning, known as quadrants, has an effect on how the address space is used.</description>
      <pubDate>Sat, 12 Sep 2009 16:57:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496370#M364290</guid>
      <dc:creator>Hakki Aydin Ucar</dc:creator>
      <dc:date>2009-09-12T16:57:27Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz_64bit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496371#M364291</link>
      <description>&amp;gt;Hakki: HP-UX currently uses only 44 of the 64 bits.&lt;BR /&gt;&lt;BR /&gt;This is most likely a hardware restriction, not software.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;that HP-UX uses the memory partitioning, known as quadrants&lt;BR /&gt;&lt;BR /&gt;This is for PA or Integrity 32 bit.  For 64 bit, there are octants and that comes the high order bits.</description>
      <pubDate>Sun, 13 Sep 2009 03:03:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496371#M364291</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-09-13T03:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz_64bit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496372#M364292</link>
      <description>Could you pls. explain what is difference between:&lt;BR /&gt;&lt;BR /&gt;maxssiz &lt;BR /&gt;maxtsiz&lt;BR /&gt;&lt;BR /&gt;Regards,</description>
      <pubDate>Sun, 13 Sep 2009 08:30:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496372#M364292</guid>
      <dc:creator>John Ferro</dc:creator>
      <dc:date>2009-09-13T08:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz_64bit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496373#M364293</link>
      <description>&amp;gt;John:&lt;BR /&gt;&lt;BR /&gt;maxtsiz: the maximum size of a code/text segment&lt;BR /&gt;&lt;BR /&gt;maxdsiz: the maximum size of the user/private data segment&lt;BR /&gt;&lt;BR /&gt;maxssiz: the maximum size of the user stack segment&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Dennis: This is for PA or Integrity 32 bit. For 64 bit, there are octants and that comes the high order bits.&lt;BR /&gt;&lt;BR /&gt;probably you are right, my notes seem little bit older. do you know any document about this topic recent updated ? &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 13 Sep 2009 08:59:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496373#M364293</guid>
      <dc:creator>Hakki Aydin Ucar</dc:creator>
      <dc:date>2009-09-13T08:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz_64bit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496374#M364294</link>
      <description>&amp;gt;Hakki: do you know any document about this topic recent updated?&lt;BR /&gt;&lt;BR /&gt;It should be directly related to the Itanium hardware and instruction set.</description>
      <pubDate>Mon, 14 Sep 2009 02:10:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496374#M364294</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-09-14T02:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz_64bit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496375#M364295</link>
      <description>&lt;A href="http://h20338.www2.hp.com/hpux11i/downloads/aas_white_paper.pdf" target="_blank"&gt;http://h20338.www2.hp.com/hpux11i/downloads/aas_white_paper.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Mon, 14 Sep 2009 10:39:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz-64bit/m-p/4496375#M364295</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2009-09-14T10:39:38Z</dc:date>
    </item>
  </channel>
</rss>

