public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Linus Torvalds <torvalds@transmeta.com>,
	"David S. Miller" <davem@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: please revert bogus patch to vmscan.c
Date: Tue, 30 Oct 2001 18:00:23 +0100	[thread overview]
Message-ID: <20011030180023.L1340@athlon.random> (raw)
In-Reply-To: <20011030162008.G1340@athlon.random> <Pine.LNX.4.33L.0110301324410.2963-100000@imladris.surriel.com> <20011030165119.I1340@athlon.random> <20011030113410.A29266@redhat.com>
In-Reply-To: <20011030113410.A29266@redhat.com>; from bcrl@redhat.com on Tue, Oct 30, 2001 at 11:34:10AM -0500

On Tue, Oct 30, 2001 at 11:34:10AM -0500, Benjamin LaHaise wrote:
> I'm contending is that the Real World difference between the correct 
> version of the optimization will have no significant performance effects 
> compared to the incorrect version that you and davem are so gleefully 
> advocating.  This means not running through "bullshit" benchmarks that 
> test one and only one thing, but running apps that actually put memory 
> pressure on the system (Oracle does so quite nicely using a filesystem 
> without O_DIRECT) which in turn causes page scanning (aka the clearing 
> of the referenced bit which is *THE* code that is being contested) but 
> should not cause swap out.  To me, this is just part of the methodology 
> of being thorough in testing the effects of changes to the VM subsystem.

There should be no relevant pagetable scanning during those tests, and
the few bits that can get unmapped have lots of time to get mapped in
again from the cache with a minor fault, IMHO there's no way such tlb
flush removal can make a difference in a DBMS workload on a sanely setup
machine, I'm amazed you think it can make a difference.

Andrea

  reply	other threads:[~2001-10-30 17:00 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 23:08 please revert bogus patch to vmscan.c Benjamin LaHaise
2001-10-29 23:14 ` David S. Miller
2001-10-29 23:15   ` Benjamin LaHaise
2001-10-29 23:25     ` Linus Torvalds
2001-10-29 23:33       ` Benjamin LaHaise
2001-10-29 23:36         ` David S. Miller
2001-10-29 23:39           ` Benjamin LaHaise
2001-10-29 23:41             ` Linus Torvalds
2001-10-29 23:48               ` Benjamin LaHaise
2001-10-29 23:50                 ` David S. Miller
2001-10-29 23:51                   ` Benjamin LaHaise
2001-10-29 23:55                     ` David S. Miller
2001-10-29 23:57                       ` Benjamin LaHaise
2001-10-30  0:01                         ` David S. Miller
2001-10-30  0:05                           ` Benjamin LaHaise
2001-10-29 23:58                       ` Linus Torvalds
2001-10-30  1:31                   ` Rik van Riel
2001-10-30  1:34                     ` David S. Miller
2001-10-30  1:42                       ` Linus Torvalds
2001-10-30  1:46                         ` David S. Miller
2001-10-30  2:25                         ` Benjamin LaHaise
2001-10-30 15:20                           ` Andrea Arcangeli
2001-10-30 15:34                             ` Rik van Riel
2001-10-30 15:51                               ` Andrea Arcangeli
2001-10-30 16:34                                 ` Benjamin LaHaise
2001-10-30 17:00                                   ` Andrea Arcangeli [this message]
2001-10-30 17:07                                     ` Rik van Riel
2001-10-30 16:13                               ` Giuliano Pochini
2001-10-30 16:54                                 ` Andrea Arcangeli
2001-10-30 17:23                                   ` Giuliano Pochini
2001-10-30 17:30                                     ` Andrea Arcangeli
2001-10-31  0:38                                       ` Paul Mackerras
     [not found]                                       ` <15327.8495.767553.389519@cargo.ozlabs.ibm.com>
2001-10-31  1:57                                         ` Andrea Arcangeli
2001-10-30 16:38                               ` Linus Torvalds
2001-10-30 16:47                                 ` Benjamin LaHaise
2001-10-30 16:57                                 ` Victor Yodaiken
2001-10-30 17:16                                   ` Troy Benjegerdes
2001-10-30 17:17                                   ` Linus Torvalds
2001-10-30 17:51                                     ` Victor Yodaiken
2001-10-30 18:01                                     ` Cort Dougan
2001-10-30 21:39                                   ` Paul Mackerras
2001-10-30 22:36                                     ` Victor Yodaiken
2001-10-30 17:23                                 ` Benjamin Herrenschmidt
2001-10-30 17:36                                   ` Benjamin Herrenschmidt
2001-10-30 17:41                                   ` Linus Torvalds
2001-10-30  1:49                       ` Benjamin LaHaise
2001-10-30  9:03                   ` Alan Cox
2001-10-29 23:22   ` Linus Torvalds
2001-10-29 23:29     ` Benjamin LaHaise
2001-10-29 23:44       ` Linus Torvalds
2001-10-30  0:02       ` Hugh Dickins
2001-10-30  0:04         ` Linus Torvalds
2001-10-30  0:04         ` David S. Miller
2001-10-29 23:51 ` Paul Mackerras

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=20011030180023.L1340@athlon.random \
    --to=andrea@suse.de \
    --cc=bcrl@redhat.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --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