public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: riel@conectiva.com.br, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org
Subject: Re: please revert bogus patch to vmscan.c
Date: Mon, 29 Oct 2001 20:49:01 -0500	[thread overview]
Message-ID: <20011029204901.A17506@redhat.com> (raw)
In-Reply-To: <20011029.155056.23033599.davem@redhat.com> <Pine.LNX.4.33L.0110292329560.2963-100000@imladris.surriel.com> <20011029.173400.35036258.davem@redhat.com>
In-Reply-To: <20011029.173400.35036258.davem@redhat.com>; from davem@redhat.com on Mon, Oct 29, 2001 at 05:34:00PM -0800

On Mon, Oct 29, 2001 at 05:34:00PM -0800, David S. Miller wrote:
> I'm asking him to show the case that "breaks for something
> else".

Why don't you try lifting your fingers to defend your position?  We know 
that:

	1. the change introduces state data to tlb with no limits on the 
	   duration of said stale data
	2. some architectures have large tlbs.

For the sake of (2), hashed tlbs count as excessively large tlbs.  See the 
UML, ia64 and powerpcs for this kind of setup.

Now, if you want to live in microbenchmark land, then, yes, the "optimized" 
but invalid behaviour will *always* win.  Back in the real world, sure, I can 
construct a microbenchmark that will sit on 2 pages of memory spinning until 
the pages get swapped out.  What does that buy us?  Nothing other than 
placating you.

I've already pointed out that the optimization can be done in a valid way.  If 
you can't go through the effort of completing the above thought experiment on 
your own, then I really have no reason to care about your opinion any further.  
You've already stated you don't care about mine, and I've stated that I don't 
feel like going to the effort to placate you.  Where does that leave us?  
Nowhere, I guess.

		-ben

  parent reply	other threads:[~2001-10-30  1:48 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
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 [this message]
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=20011029204901.A17506@redhat.com \
    --to=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