linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	Mel Gorman <mel@csn.ul.ie>, Johannes Weiner <jweiner@redhat.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] remove compaction from kswapd
Date: Tue, 1 Mar 2011 16:41:43 -0800	[thread overview]
Message-ID: <20110301164143.e44e5699.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTim7tcPTxG9hyFiSnQ7rqfMdoUhL1wrmqNAXAvEK@mail.gmail.com>

On Wed, 2 Mar 2011 08:10:35 +0900
Minchan Kim <minchan.kim@gmail.com> wrote:

> On Wed, Mar 2, 2011 at 7:39 AM, Andrea Arcangeli <aarcange@redhat.com> wrote:
> > On Wed, Mar 02, 2011 at 07:33:13AM +0900, Minchan Kim wrote:
> >> Sorry for bothering you but I think you get the data.
> >> It helps someone in future very much to know why we determined to
> >> remove the feature at that time and they should do what kinds of
> >> experiment to prove it has a benefit to add compaction in kswapd
> >> again.
> >
> > This is a benchmark I'm unsure if it's ok to publish results but it
> > should be possible to simulate it with a device driver.
> >
> > Arthur provided kswapd load usage data too, so I hope that's enough.
> >
> > My other patch (compaction-kswapd-3) is way better than current logic
> > and retains compaction in kswapd. That shows slightly higher
> > kswapd utilization with Arthur's multimedia workload, and a bit worse
> > performance on the network benchmark. So I thought it was better to go
> > with the fastest potion as long as we don't have a logic that uses
> > compaction and shows improved performance and lower latency than with
> > no compaction at all in kswapd.
> >
> 
> I didn't notice Arthur's problem.
> The patch seems to fix a real problem so I think it's enough.
> I wished you wrote down the link url about Arthur on LKML.
> 
> You can remove compact_mode of compact_control.
> Otherwise, looks good to me.
> 

I'd be pretty worried about jamming this into 2.6.38 at this late
stage.  And some vague talk about something Arthur did really doesn't
help a lot!  It would be better to have some good, solid quantitative
justification for what is really an emergency patch.  

Bear in mind that we always have a middle option: merge a patch into
2.6.39-rc1 and tag it for backporting into 2.6.38.x.  That gives us
more time to test it and to generally give it a shakedown.  But to make
decisions like that and to commend a patch to the -stable maintainers,
we need to provide better information please.

Also, "This goes on top of the two lowlatency fixes for compaction"
isn't particularly helpful.  I need to verify that the referred-to
patches are already in mainline but I don't have a clue what this
description refers to.  More specificity, please - it helps avoid
mistakes.

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-03-02  0:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 22:21 [PATCH] remove compaction from kswapd Andrea Arcangeli
2011-03-01 22:33 ` Minchan Kim
2011-03-01 22:39   ` Andrea Arcangeli
2011-03-01 23:10     ` Minchan Kim
2011-03-02  0:41       ` Andrew Morton [this message]
2011-03-02  4:38         ` Andrea Arcangeli
2011-03-02  4:39           ` Andrea Arcangeli
2011-03-02  4:53           ` Andrew Morton
2011-03-02  5:52             ` Andrea Arcangeli
2011-03-02  5:57               ` Andrew Morton
2011-03-02 17:21                 ` Andrea Arcangeli
2011-03-02 14:25               ` Mel Gorman
2011-03-09 22:17                 ` Andrew Morton
2011-03-09 23:50                   ` Andrea Arcangeli
2011-03-10 10:11                     ` Mel Gorman
2011-03-09 17:00         ` 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=20110301164143.e44e5699.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aarcange@redhat.com \
    --cc=jweiner@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=minchan.kim@gmail.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;
as well as URLs for NNTP newsgroup(s).