All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: use pagevec to rotate reclaimable page
Date: Wed, 19 Sep 2007 15:17:45 -0700	[thread overview]
Message-ID: <20070919151745.1e12a671.akpm@linux-foundation.org> (raw)
In-Reply-To: <6.0.0.20.2.20070918193944.038e2ea0@172.19.0.2>

On Tue, 18 Sep 2007 19:41:14 +0900
Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp> wrote:

>  >
>  >So I do think that for safety and sanity's sake, we should be taking a ref
>  >on the pages when they are in a pagevec.  That's going to hurt your nice
>  >performance numbers :(
>  >
> 
> I did ping test again to observe performance deterioration caused by taking 
> a ref.
> 
> 	-2.6.23-rc6-with-modifiedpatch
> 	--- testmachine ping statistics ---
> 	3000 packets transmitted, 3000 received, 0% packet loss, time 53386ms
> 	rtt min/avg/max/mdev = 0.074/0.110/4.716/0.147 ms, pipe 2, ipg/ewma 
> 17.801/0.129 ms
> 
> The result for my original patch is as follows.
> 
> 	-2.6.23-rc5-with-originalpatch
> 	--- testmachine ping statistics ---
> 	3000 packets transmitted, 3000 received, 0% packet loss, time 51924ms
> 	rtt min/avg/max/mdev = 0.072/0.108/3.884/0.114 ms, pipe 2, ipg/ewma 
> 17.314/0.091 ms
> 
> 
> The influence to response was small.

well.. that's not really the test which will show up any regressions.

The extra get_page/put_page will affect things like kernel CPU utilisation
on fast writeout on a single CPU.  Say, run a huge write against a fast
storage system on a single pentium 4 CPU and see how much the system CPU
time is increased.

The kernel's internal cpu accounting probably won't be accurate enough to
get believeable numbers from a test like this - better to use the
subtractive approach: see http://www.zipworld.com.au/~akpm/linux/#zc

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: use pagevec to rotate reclaimable page
Date: Wed, 19 Sep 2007 15:17:45 -0700	[thread overview]
Message-ID: <20070919151745.1e12a671.akpm@linux-foundation.org> (raw)
In-Reply-To: <6.0.0.20.2.20070918193944.038e2ea0@172.19.0.2>

On Tue, 18 Sep 2007 19:41:14 +0900
Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp> wrote:

>  >
>  >So I do think that for safety and sanity's sake, we should be taking a ref
>  >on the pages when they are in a pagevec.  That's going to hurt your nice
>  >performance numbers :(
>  >
> 
> I did ping test again to observe performance deterioration caused by taking 
> a ref.
> 
> 	-2.6.23-rc6-with-modifiedpatch
> 	--- testmachine ping statistics ---
> 	3000 packets transmitted, 3000 received, 0% packet loss, time 53386ms
> 	rtt min/avg/max/mdev = 0.074/0.110/4.716/0.147 ms, pipe 2, ipg/ewma 
> 17.801/0.129 ms
> 
> The result for my original patch is as follows.
> 
> 	-2.6.23-rc5-with-originalpatch
> 	--- testmachine ping statistics ---
> 	3000 packets transmitted, 3000 received, 0% packet loss, time 51924ms
> 	rtt min/avg/max/mdev = 0.072/0.108/3.884/0.114 ms, pipe 2, ipg/ewma 
> 17.314/0.091 ms
> 
> 
> The influence to response was small.

well.. that's not really the test which will show up any regressions.

The extra get_page/put_page will affect things like kernel CPU utilisation
on fast writeout on a single CPU.  Say, run a huge write against a fast
storage system on a single pentium 4 CPU and see how much the system CPU
time is increased.

The kernel's internal cpu accounting probably won't be accurate enough to
get believeable numbers from a test like this - better to use the
subtractive approach: see http://www.zipworld.com.au/~akpm/linux/#zc

--
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>

  parent reply	other threads:[~2007-09-19 22:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11  9:31 [PATCH] mm: use pagevec to rotate reclaimable page Hisashi Hifumi
2007-09-11  9:31 ` Hisashi Hifumi
2007-09-14  2:37 ` Andrew Morton
2007-09-14  2:37   ` Andrew Morton
2007-09-14  7:42   ` Hisashi Hifumi
2007-09-14  7:42     ` Hisashi Hifumi
2007-09-18 10:41   ` Hisashi Hifumi
2007-09-18  1:29     ` Nick Piggin
2007-09-18  1:29       ` Nick Piggin
2007-09-18 17:44       ` Andrew Morton
2007-09-18 17:44         ` Andrew Morton
2007-09-18  1:47         ` Nick Piggin
2007-09-18  1:47           ` Nick Piggin
2007-09-18 18:03           ` Andrew Morton
2007-09-18 18:03             ` Andrew Morton
2007-09-19 22:17     ` Andrew Morton [this message]
2007-09-19 22:17       ` Andrew Morton

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=20070919151745.1e12a671.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hifumi.hisashi@oss.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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.