<?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: mmap limitation in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888881#M3512</link>
    <description>Can't help there.  If you can't get your answer from the Kernel source directly, you might want to ask in a kernel developers list (see &lt;A href="http://www.kernel.org/" target="_blank"&gt;http://www.kernel.org/&lt;/A&gt; under 'Mailing Lists'), or spend some time with google.</description>
    <pubDate>Thu, 23 Jan 2003 21:55:46 GMT</pubDate>
    <dc:creator>Stuart Browne</dc:creator>
    <dc:date>2003-01-23T21:55:46Z</dc:date>
    <item>
      <title>mmap limitation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888878#M3509</link>
      <description>Does any know if there is a limitation on how much mmap can allocate? What is the max memory can mmap allocate? FYI, I am running with 4Gbytes and 1Gbytes of swap. The flavor is RedHat 7.3 running kernel 2.4.18. Thanks.</description>
      <pubDate>Thu, 23 Jan 2003 03:50:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888878#M3509</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2003-01-23T03:50:14Z</dc:date>
    </item>
    <item>
      <title>Re: mmap limitation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888879#M3510</link>
      <description>According to documentation and kernel-source:&lt;BR /&gt;&lt;BR /&gt;man mmap:&lt;BR /&gt;void  *  mmap(void *start, size_t length, int prot , int flags, int fd, off_t offset);&lt;BR /&gt;&lt;BR /&gt;linux/types.h&lt;BR /&gt;typedef __kernel_size_t size_t;&lt;BR /&gt;&lt;BR /&gt;asm/posix_types.h&lt;BR /&gt;typedef unsigned int    __kernel_size_t;&lt;BR /&gt;&lt;BR /&gt;So..  How long is an unsigned int these days?&lt;BR /&gt;&lt;BR /&gt;With a bit of creativity, limits.h reports:&lt;BR /&gt;&lt;BR /&gt;/* Maximum value an `unsigned int' can hold.  (Minimum is 0.)  */&lt;BR /&gt;#  define UINT_MAX      4294967295U&lt;BR /&gt;&lt;BR /&gt;Now, as to whether there is any other sort of limitation in place, I'm unsure.  You'd have to poke through the kernel documentation.  I recall limitations on memory page sizes for non-enterprise kernel builds.&lt;BR /&gt;</description>
      <pubDate>Thu, 23 Jan 2003 04:31:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888879#M3510</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2003-01-23T04:31:06Z</dc:date>
    </item>
    <item>
      <title>Re: mmap limitation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888880#M3511</link>
      <description>Is there a way (like kerneal tunable parameter) to tell the system that I can use more than 2 gbytes when using mmap, since my physical memory is 4gbytes and swap is 1Gbytes. Thanks.</description>
      <pubDate>Thu, 23 Jan 2003 15:18:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888880#M3511</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2003-01-23T15:18:48Z</dc:date>
    </item>
    <item>
      <title>Re: mmap limitation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888881#M3512</link>
      <description>Can't help there.  If you can't get your answer from the Kernel source directly, you might want to ask in a kernel developers list (see &lt;A href="http://www.kernel.org/" target="_blank"&gt;http://www.kernel.org/&lt;/A&gt; under 'Mailing Lists'), or spend some time with google.</description>
      <pubDate>Thu, 23 Jan 2003 21:55:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888881#M3512</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2003-01-23T21:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: mmap limitation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888882#M3513</link>
      <description>All,&lt;BR /&gt;I have not gotten back into investigating max limitation on kernel2.4 regarding how much sharemem can mmap allocate? But now I am looking into something similar and I am wondering if some one could shed some lights onto this.  Here's what bother me, when I check the sharemem list via ipcs I do not see the expected sharemem on the list.  But according to top, my application has allocated 400Mbytes of share memory (which is allocated via mmap). could any one explain why top see the sharemem where as ipcs does not see the sharemem which our application has allocated.</description>
      <pubDate>Mon, 12 Jan 2004 20:43:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mmap-limitation/m-p/2888882#M3513</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2004-01-12T20:43:43Z</dc:date>
    </item>
  </channel>
</rss>

