From: Yoann Vandoorselaere <yoann@mandrakesoft.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: andrea@e-mind.com, Mark Hemment <markhe@veritas.com>,
Jens Axboe <axboe@kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] 4GB I/O, cut three
Date: 30 May 2001 20:57:50 +0200 [thread overview]
Message-ID: <87r8x6k6kx.fsf@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0105301542210.12540-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0105301542210.12540-100000@imladris.rielhome.conectiva>
Rik van Riel <riel@conectiva.com.br> writes:
> On Wed, 30 May 2001 andrea@e-mind.com wrote:
>
> > btw, I think such heuristic is horribly broken ;), the highmem zone
> > simply needs to be balanced if it is under the pages_low mark, just
> > skipping it and falling back into the normal zone that happens to be
> > above the low mark is the wrong thing to do.
>
> 2.3.51 did this, we all know the result.
Just a note,
I remember the 2.3.51 kernel as the most usable kernel I ever used
talking about VM.
--
Yoann Vandoorselaere | C makes it easy to shoot yourself in the foot. C++ makes
MandrakeSoft | it harder, but when you do, it blows away your whole
| leg. - Bjarne Stroustrup
next prev parent reply other threads:[~2001-05-30 18:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 14:07 [patch] 4GB I/O, cut three Jens Axboe
2001-05-29 14:11 ` Jens Axboe
2001-05-30 9:43 ` Mark Hemment
2001-05-30 9:55 ` Jens Axboe
2001-05-30 10:59 ` Mark Hemment
2001-05-30 14:26 ` andrea
2001-05-30 18:42 ` Rik van Riel
2001-05-30 18:57 ` Andrea Arcangeli
2001-05-30 18:57 ` Yoann Vandoorselaere [this message]
2001-05-30 19:18 ` Andrea Arcangeli
2001-05-30 19:23 ` Rik van Riel
2001-05-30 14:00 ` Andrea Arcangeli
2001-05-30 14:06 ` Jens Axboe
2001-05-30 18:36 ` Rik van Riel
2001-05-30 13:03 ` Mark Hemment
2001-05-30 13:24 ` Jens Axboe
2001-05-30 13:37 ` Mark Hemment
2001-05-30 13:40 ` Jens Axboe
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=87r8x6k6kx.fsf@mandrakesoft.com \
--to=yoann@mandrakesoft.com \
--cc=andrea@e-mind.com \
--cc=axboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markhe@veritas.com \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.