public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>, Lee Revell <rlrevell@joe-job.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix free swap cache latency
Date: Thu, 16 Mar 2006 23:07:58 +0100	[thread overview]
Message-ID: <20060316220758.GA27349@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.61.0603161853300.24463@goblin.wat.veritas.com>


* Hugh Dickins <hugh@veritas.com> wrote:

> Lee Revell reported 28ms latency when process with lots of swapped memory
> exits.
> 
> 2.6.15 introduced a latency regression when unmapping: in accounting the
> zap_work latency breaker, pte_none counted 1, pte_present PAGE_SIZE, but
> a swap entry counted nothing at all.  We think of pages present as the
> slow case, but Lee's trace shows that free_swap_and_cache's radix tree
> lookup can make a lot of work - and we could have been doing it many
> thousands of times without a latency break.
> 
> Move the zap_work update up to account swap entries like pages present.
> This does account non-linear pte_file entries, and unmap_mapping_range
> skipping over swap entries, by the same amount even though they're quick:
> but neither of those cases deserves complicating the code (and they're
> treated no worse than they were in 2.6.14).
> 
> Signed-off-by: Hugh Dickins <hugh@veritas.com>
> Acked-by: Nick Piggin <npiggin@suse.de>

i've added this patch to the 2.6.16-rc6 based -rt kernel yesterday and 
have ran an overnight stresstest on an SMP box (which creates heavy 
swapping too, amongst other things), which found no problems whatsoever.  
(not that we would expect any, but it's still nice to know.)

Acked-by: Ingo Molnar <mingo@elte.hu>

	Ingo

  reply	other threads:[~2006-03-16 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16 19:11 [PATCH] fix free swap cache latency Hugh Dickins
2006-03-16 22:07 ` Ingo Molnar [this message]
2006-03-17  1:38 ` Andrew Morton
2006-03-17  2:52   ` Nick Piggin
2006-03-17 17:55     ` Hugh Dickins

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=20060316220758.GA27349@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=rlrevell@joe-job.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