From: Rik van Riel <riel@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.redhat.com, linux-mm@kvack.org,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: TODO list for new VM (oct 2000)
Date: Mon, 2 Oct 2000 15:34:49 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0010021531360.22539-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.21.0010021524140.22539-100000@duckman.distro.conectiva>
On Mon, 2 Oct 2000, Rik van Riel wrote:
> On Mon, 2 Oct 2000, Linus Torvalds wrote:
>
> > Why do you apparently ignore the fact that page-out write-back
> > performance is horribly crappy because it always starts out
> > doing synchronous writes?
>
> Because it is fixed in the patch I mailed yesterday?
One small warning though. Please don't apply that patch
yet because I fixed 3 more small problems today. I'll
send you an updated patch...
- the compile warnings are fixed
- in try_to_free_pages(), we forgot to set
PF_MEMALLOC in current->flags (oops)
- in grow_buffers(), in case we cannot get a
buffer head, we must unlock the page
A patch against 2.4.0-test9-pre8 with these 3 changes will
be on its way once I've tested it a bit...
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
--
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/
next prev parent reply other threads:[~2000-10-02 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-02 18:01 Rik van Riel
2000-10-02 18:20 ` Linus Torvalds
2000-10-02 18:24 ` Rik van Riel
2000-10-02 18:34 ` Rik van Riel [this message]
2000-10-05 1:08 ` Matthew Dillon
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.4.21.0010021531360.22539-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=dillon@apollo.backplane.com \
--cc=linux-kernel@vger.redhat.com \
--cc=linux-mm@kvack.org \
--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