From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: Bill Hawes <whawes@star.net>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: minor patch for 2.1.90 fs/buffer.c
Date: Tue, 24 Mar 1998 21:17:55 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980324211627.1182D-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <35180539.13BA0CD8@star.net>
On Tue, 24 Mar 1998, Bill Hawes wrote:
> allocation would be required. (I recently observed a machine with 500M of RAM,
> heavily swapping, but with only 360 buffers, so this situation can occur.)
Indeed, you're completely right... I've noticed something like
this as well, although not as severe.
But maybe we should _limit_ the second-round allocation to
something less than half of the needed buffermem (say, 1/4th).
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.fys.ruu.nl/~riel/ | <H.H.vanRiel@fys.ruu.nl> |
+-------------------------------------------+--------------------------+
parent reply other threads:[~1998-03-24 21:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <35180539.13BA0CD8@star.net>]
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.91.980324211627.1182D-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.com \
--cc=whawes@star.net \
/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