All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Joel Schopp <jschopp@austin.ibm.com>
Cc: Mel Gorman <mel@csn.ul.ie>, Andrew Morton <akpm@osdl.org>,
	kravetz@us.ibm.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	lhms <lhms-devel@lists.sourceforge.net>
Subject: Re: [PATCH 6/8] Fragmentation Avoidance V17: 006_largealloc_tryharder
Date: Thu, 13 Oct 2005 22:36:27 -0700	[thread overview]
Message-ID: <1129268188.22903.34.camel@localhost> (raw)
In-Reply-To: <434EB058.8090809@austin.ibm.com>

On Thu, 2005-10-13 at 14:07 -0500, Joel Schopp wrote:
> This is version 17, plus several versions I did while Mel was preoccupied with 
> his day job, makes well over 20 times this has been posted to the mailing lists 
> that are lkml, linux-mm, and memory hotplug.
> 
> All objections/feedback/suggestions that have been brought up on the lists are 
> fixed in the following version.  It's starting to become almost silent when a 
> new version gets posted, possibly because everybody accepts the code as perfect, 
> possibly because they have grown bored with it.  Probably a combination of both.

I don't think it's shown signs of stabilizing quite yet.  Each revision
has new code that needs to be cleaned up, and new obvious CodingStyle
issues.  Let's see a couple of incrementally cleaner releases go by,
which don't have renewed old issues, and then we can think about asking
to get it merged elsewhere.

-- Dave


WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Joel Schopp <jschopp@austin.ibm.com>
Cc: Mel Gorman <mel@csn.ul.ie>, Andrew Morton <akpm@osdl.org>,
	kravetz@us.ibm.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	lhms <lhms-devel@lists.sourceforge.net>
Subject: Re: [PATCH 6/8] Fragmentation Avoidance V17: 006_largealloc_tryharder
Date: Thu, 13 Oct 2005 22:36:27 -0700	[thread overview]
Message-ID: <1129268188.22903.34.camel@localhost> (raw)
In-Reply-To: <434EB058.8090809@austin.ibm.com>

On Thu, 2005-10-13 at 14:07 -0500, Joel Schopp wrote:
> This is version 17, plus several versions I did while Mel was preoccupied with 
> his day job, makes well over 20 times this has been posted to the mailing lists 
> that are lkml, linux-mm, and memory hotplug.
> 
> All objections/feedback/suggestions that have been brought up on the lists are 
> fixed in the following version.  It's starting to become almost silent when a 
> new version gets posted, possibly because everybody accepts the code as perfect, 
> possibly because they have grown bored with it.  Probably a combination of both.

I don't think it's shown signs of stabilizing quite yet.  Each revision
has new code that needs to be cleaned up, and new obvious CodingStyle
issues.  Let's see a couple of incrementally cleaner releases go by,
which don't have renewed old issues, and then we can think about asking
to get it merged elsewhere.

-- Dave

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-10-14  5:36 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 15:12 [PATCH 0/8] Fragmentation Avoidance V17 Mel Gorman
2005-10-11 15:12 ` Mel Gorman
2005-10-11 15:12 ` [PATCH 1/8] Fragmentation Avoidance V17: 001_antidefrag_flags Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-11 15:12 ` [PATCH 2/8] Fragmentation Avoidance V17: 002_usemap Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-13 13:56   ` Dave Hansen
2005-10-13 13:56     ` Dave Hansen
2005-10-13 14:10     ` Mel Gorman
2005-10-13 14:10       ` Mel Gorman
2005-10-13 14:18       ` Dave Hansen
2005-10-13 14:18         ` Dave Hansen
2005-10-13 14:35         ` Mel Gorman
2005-10-13 14:35           ` Mel Gorman
2005-10-16 20:44         ` Mel Gorman
2005-10-16 20:44           ` Mel Gorman
2005-10-13 16:33       ` Joel Schopp
2005-10-13 16:33         ` Joel Schopp
2005-10-11 15:12 ` [PATCH 3/8] Fragmentation Avoidance V17: 003_fragcore Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-11 15:12 ` [PATCH 4/8] Fragmentation Avoidance V17: 004_markfree Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-11 15:12 ` [PATCH 5/8] Fragmentation Avoidance V17: 005_fallback Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-12 16:43   ` mike kravetz
2005-10-12 16:43     ` mike kravetz
2005-10-12 17:21     ` Mel Gorman
2005-10-12 17:21       ` Mel Gorman
2005-10-12 17:29       ` [Lhms-devel] " Joel Schopp
2005-10-12 17:29         ` Joel Schopp
2005-10-14  5:12         ` Dave Hansen
2005-10-14  5:12           ` Dave Hansen
2005-10-11 15:12 ` [PATCH 6/8] Fragmentation Avoidance V17: 006_largealloc_tryharder Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-13 19:07   ` Joel Schopp
2005-10-13 19:07     ` Joel Schopp
2005-10-14  5:36     ` Dave Hansen [this message]
2005-10-14  5:36       ` Dave Hansen
2005-10-11 15:12 ` [PATCH 7/8] Fragmentation Avoidance V17: 007_percpu Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-11 15:13 ` [PATCH 8/8] Fragmentation Avoidance V17: 008_stats Mel Gorman
2005-10-11 15:13   ` Mel Gorman
2005-10-12 11:57   ` [Lhms-devel] " Dave Hansen
2005-10-12 11:57     ` Dave Hansen
2005-10-12 12:19     ` Mel Gorman
2005-10-12 12:19       ` Mel Gorman
2005-10-16  2:52 ` [PATCH 0/8] Fragmentation Avoidance V17 Paul Jackson
2005-10-16  2:52   ` Paul Jackson
2005-10-16 11:59   ` Mel Gorman
2005-10-16 11:59     ` Mel Gorman
2005-10-16 17:53     ` Paul Jackson
2005-10-16 17:53       ` Paul Jackson
2005-10-16 18:03       ` Mel Gorman
2005-10-16 18:03         ` Mel Gorman

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=1129268188.22903.34.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=jschopp@austin.ibm.com \
    --cc=kravetz@us.ibm.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.