From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,be7fa91648ac3f12 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!newsread.com!newsprint.newsread.com!news-feed01.roc.ny.frontiernet.net!nntp.frontiernet.net!newscon06.news.prodigy.com!prodigy.net!newsfeed-00.mathworks.com!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Large arrays (again), problem case for GNAT Date: 15 Apr 2005 15:06:43 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls4.std.com 1113592003 32719 192.74.137.71 (15 Apr 2005 19:06:43 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Fri, 15 Apr 2005 19:06:43 +0000 (UTC) User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: g2news1.google.com comp.lang.ada:10503 Date: 2005-04-15T15:06:43-04:00 List-Id: Mark Lorenzen writes: > A simple "man malloc" specifies that the default overcommitting > behaviour can be turned of by writing the letter "2" to the file > /proc/sys/vm/overcommit_memory . F.x.: > > echo 2 > /proc/sys/vm/overcommit_memory Well, that's not much use. Whether you want to overcommit depends on the situation. Some programs are written with overcommit in mind, so you can't just globally turn it off. Ideally, it would be controllable on a per-object basis. It should be controlled by the programmer, not by the user/system-administrator. Not just heap objects, either. I'd like to have overcommit for statically allocated (library level) variables, so I'd want to be able to turn that off or on. - Bob