mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andrea Arcangeli <andrea@suse.de>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre8aa3
Date: Thu, 16 May 2002 20:26:26 +0100	[thread overview]
Message-ID: <20020516202626.A13795@infradead.org> (raw)
In-Reply-To: <20020515212733.GA1025@dualathlon.random>

On Wed, May 15, 2002 at 11:27:33PM +0200, Andrea Arcangeli wrote:
> o	minor bdflush tuning difference to avoid char-writer in bonnie
> 	to stall and to slowdown too much (can make a difference in real
> 	life)

...

> Only in 2.4.19pre8aa3: 00_bdflush-tuning-1
> 
> 	Put the mid watermark at 50% (near the high watermark so we don't stall
> 	too much).

As the 2.4.19-pre mainline got your buffer throtteling changes I guess it
has the same issues?  Do you think it's worth to submit that patch to Marcelo
even that late in the release cycle?

> Only in 2.4.19pre8aa2: 05_vm_10_read_write_tweaks-1
> Only in 2.4.19pre8aa3: 05_vm_10_read_write_tweaks-2
> 
> 	Avoid backing out the flush_page_to_ram in this vm patch,
> 	the one on the pagecache is still needed before the memcpy
> 	on the pagecache during the early cow (would be cleaner
> 	to move it up, if Hugh wants to clean it up that's welcome,
> 	it will be an orthogonal patch, so far I just avoid to
> 	change that area in my changes, not high prio to clean it up
> 	as DaveM side it's more high prio to conver the users of
> 	flush_page_to_ram API to flush_dcache_page/icache new API during 2.5).

It seems to me you ignore the comments akpm put in the split patches you
merged :)  Not only the comment to this change is superflous now, but also
I'd really like to get an answer to the remaining part of it as Andrew's
comment about that part beeing buggy makes a lot of sense to me..


  parent reply	other threads:[~2002-05-16 19:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 21:27 2.4.19pre8aa3 Andrea Arcangeli
2002-05-15 21:56 ` 2.4.19pre8aa3 Andreas Dilger
2002-05-16  2:18   ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-15 22:30 ` 2.4.19pre8aa3 Rik van Riel
2002-05-16  2:01   ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16  2:06     ` 2.4.19pre8aa3 Rik van Riel
2002-05-16  2:32       ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16  2:42         ` 2.4.19pre8aa3 Rik van Riel
2002-05-16  2:58           ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16  8:36         ` 2.4.19pre8aa3 Russell King
2002-05-16  8:59           ` 2.4.19pre8aa3 Russell King
2002-05-16 12:56           ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16  9:27         ` 2.4.19pre8aa3 Juan Quintela
2002-05-16 16:07           ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 18:37             ` 2.4.19pre8aa3 Rik van Riel
2002-05-16 18:59               ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16  3:12     ` 2.4.19pre8aa3 Andrew Morton
2002-05-16  3:23       ` 2.4.19pre8aa3 Andrea Arcangeli
2002-05-16 19:26 ` Christoph Hellwig [this message]
2002-05-31 20:34   ` 2.4.19pre8aa3 Andrea Arcangeli

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=20020516202626.A13795@infradead.org \
    --to=hch@infradead.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®