From: Daniel Phillips <phillips@arcor.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Andrew Morton <akpm@zip.com.au>,
Rik van Riel <riel@conectiva.com.br>,
Dave McCracken <dmccr@us.ibm.com>,
Linux Memory Management <linux-mm@kvack.org>,
rwhron@earthlink.net
Subject: Re: [PATCH] Optimize out pte_chain take three
Date: Sat, 13 Jul 2002 15:55:32 +0200 [thread overview]
Message-ID: <E17TNN4-0003Iw-00@starship> (raw)
In-Reply-To: <20020713133058.GU23693@holomorphy.com>
On Saturday 13 July 2002 15:30, William Lee Irwin III wrote:
> On Sat, Jul 13, 2002 at 03:22:28PM +0200, Daniel Phillips wrote:
> > See "enables" above. Though I agree we want the thing at parity or
> > better on its own merits, I don't see the point of throwing tomatoes at
> > the "enables" points. Recommendation: separate the list into "improves"
> > and "enables".
>
> The direction has been set and I'm following it. These things are now
> off the roadmap entirely regardless, or at least I won't pursue them
> until the things needing to be done now are addressed.
> Say, we could use a number of helpers with the quantitative measurement
> effort, Is there any chance you could help out here as well?
Forget it :-)
I'll help with the test design. We have a bunch of people ready to do
the work on the actual benchmarking. We need to provide precise statements
of the test model, and put out a call for testers. I'll help with that
too.
> It'd certainly help get the cost/benefit analysis of rmap going for the
> merge, and maybe even pinpoint things needing to be addressed.
--
Daniel
--
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-mm.org/
next prev parent reply other threads:[~2002-07-13 13:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 19:04 [PATCH] Optimize out pte_chain take two Dave McCracken
2002-07-10 0:21 ` Andrew Morton
2002-07-10 14:33 ` [PATCH] Optimize out pte_chain take three Dave McCracken
2002-07-10 15:18 ` Rik van Riel
2002-07-10 17:32 ` William Lee Irwin III
2002-07-10 20:01 ` Andrew Morton
2002-07-10 20:14 ` Rik van Riel
2002-07-10 20:28 ` Andrew Morton
2002-07-10 20:38 ` Rik van Riel
2002-07-13 13:42 ` Daniel Phillips
2002-07-10 20:33 ` Martin J. Bligh
2002-07-10 22:22 ` William Lee Irwin III
2002-07-11 0:39 ` Andrew Morton
2002-07-11 0:47 ` Rik van Riel
2002-07-11 1:27 ` Andrew Morton
2002-07-13 14:10 ` Daniel Phillips
2002-07-11 1:51 ` William Lee Irwin III
2002-07-11 2:28 ` William Lee Irwin III
2002-07-11 19:54 ` Andrew Morton
2002-07-11 20:05 ` Rik van Riel
2002-07-11 20:42 ` Andrew Morton
2002-07-11 20:54 ` Rik van Riel
2002-07-11 21:16 ` Andrew Morton
2002-07-11 21:41 ` Rik van Riel
2002-07-11 22:38 ` Andrew Morton
2002-07-11 23:18 ` Rik van Riel
2002-07-12 18:27 ` Paul Larson
2002-07-12 19:06 ` Andrew Morton
2002-07-12 19:28 ` Andrew Morton
2002-07-13 15:08 ` Daniel Phillips
2002-07-11 22:54 ` William Lee Irwin III
2002-07-13 14:52 ` Daniel Phillips
2002-07-13 14:08 ` Daniel Phillips
2002-07-13 14:20 ` Daniel Phillips
2002-07-13 14:45 ` Daniel Phillips
2002-07-13 13:22 ` Daniel Phillips
2002-07-13 13:30 ` William Lee Irwin III
2002-07-13 13:55 ` Daniel Phillips [this message]
2002-07-13 13:41 ` Daniel Phillips
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=E17TNN4-0003Iw-00@starship \
--to=phillips@arcor.de \
--cc=akpm@zip.com.au \
--cc=dmccr@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=rwhron@earthlink.net \
--cc=wli@holomorphy.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