linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark_H_Johnson@Raytheon.com
To: hahn@coffee.psychology.mcmaster.ca
Cc: linux-mm@kvack.org, Wichert Akkerman <wichert@cistron.nl>
Subject: Re: Running out of memory in 1 easy step
Date: Fri, 15 Sep 2000 08:22:48 -0500	[thread overview]
Message-ID: <OF197FE829.51802B4B-ON8625695B.0048CCDB@hou.us.ray.com> (raw)

I hate to ask, but where is this behavior described?  I can't find any hint
of this behavior in the man page. I'm concerned because we would not have
taken the "guard pages" into account when sizing our application's memory
usage. We have a real time application where we will also lock the pages
into memory - running out of physical memory in this case is "very bad".
Thanks.

--Mark H Johnson
  <mailto:Mark_H_Johnson@raytheon.com>


                                                                                                                                 
                    Mark Hahn                                                                                                    
                    <hahn@coffee.psychology.mc        To:     Wichert Akkerman <wichert@cistron.nl>                              
                    master.ca>                        cc:     linux-mm@kvack.org, (bcc: Mark H Johnson/RTS/Raytheon/US)          
                                                      Subject:     Re: Running out of memory in 1 easy step                      
                    09/14/00 06:03 PM                                                                                            
                                                                                                                                 
                                                                                                                                 



> Not likely, there were still a couple hundreds of megabytes free and
> the process had allocated about 1.5Gb of data.

mmaping 1 to 4096 bytes consumes 8K from your address space:
one for the mmaped page, and one (virtual) guard page (unless
you use MAP_FIXED, of course.)  4G / 8K is approximately the 458878
you reported.  actually, since maps begin at 1G, I would have
expected you to run out sooner...

regards, mark hahn.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/




--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

             reply	other threads:[~2000-09-15 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-15 13:22 Mark_H_Johnson [this message]
2000-09-15 16:35 ` Mark Hahn
  -- strict thread matches above, loose matches on Subject: below --
2000-09-15 16:53 Mark_H_Johnson
2000-09-14 12:59 Wichert Akkerman
2000-09-14 15:56 ` Andi Kleen
2000-09-14 16:08   ` Wichert Akkerman
2000-09-14 18:43     ` Andi Kleen
2000-09-14 19:20       ` Wichert Akkerman
2000-09-14 23:03         ` Mark Hahn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OF197FE829.51802B4B-ON8625695B.0048CCDB@hou.us.ray.com \
    --to=mark_h_johnson@raytheon.com \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --cc=linux-mm@kvack.org \
    --cc=wichert@cistron.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox