From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Rik van Riel <H.H.vanRiel@fys.ruu.nl>,
"Stephen C. Tweedie" <sct@dcs.ed.ac.uk>,
linux-mm <linux-mm@kvack.org>
Subject: Re: new allocation algorithm
Date: Fri, 27 Mar 1998 13:33:06 -0500 (U\x01) [thread overview]
Message-ID: <Pine.LNX.3.95.980327131931.8105A-100000@as200.spellcast.com> (raw)
In-Reply-To: <Pine.LNX.3.95.980327092811.6613C-100000@penguin.transmeta.com>
On Fri, 27 Mar 1998, Linus Torvalds wrote:
> The current scheme is fairly efficient and extremely stable, and gives
> good behaviour for the cases we _really_ care about (pageorders 0, 1 and
> to some degree 2). It comes reasonably close to working for the higher
> orders too, but they really aren't as critical..
As a 'useful gathering of statistics' measure, could something along the
lines of the following pseudo-patch be added to 2.1.92? This way we'll
learn of any memory allocation failures, rather than syscalls failing or
SIGSEGVs occurring and people not knowing what's up.
in __get_free_pages:
nopage:
+{ static long last_nomem_jiffies, nomem_fails;
+ if ((jiffies - last_nomem_jiffies) >= 2*HZ) {
+ printk("__get_free_pages(%x, %lu) failed (%ld)\n",
+ gfp_mask, order, ++nomem_fails);
+ last_nomem_jiffies = jiffies;
+ }
+}
return 0;
-ben
next prev parent reply other threads:[~1998-03-27 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-27 9:03 Rik van Riel
1998-03-27 17:30 ` Linus Torvalds
1998-03-27 18:33 ` Benjamin C.R. LaHaise [this message]
1998-03-30 15:07 ` Rik van Riel
1998-04-01 20:28 ` Stephen C. Tweedie
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=Pine.LNX.3.95.980327131931.8105A-100000@as200.spellcast.com \
--to=blah@kvack.org \
--cc=H.H.vanRiel@fys.ruu.nl \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
--cc=torvalds@transmeta.com \
/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