All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Soeren Sandmann <sandmann@daimi.au.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add ability to dump mapped pages with /proc/sys/vm/drop_caches
Date: Sun, 30 Sep 2007 23:36:05 -0400	[thread overview]
Message-ID: <20071001033605.GA11497@redhat.com> (raw)
In-Reply-To: <ye8641s2fp4.fsf@camel11.daimi.au.dk>

On Sun, Sep 30, 2007 at 08:03:51PM +0200, Soeren Sandmann wrote:
 > This patch adds the ability to drop mapped pages with
 > /proc/sys/vm/drop_caches. This is useful to get repeatable
 > measurements of startup time for applications. 
 > 
 > Without it, pages that are mapped in already-running applications will
 > not get dropped, so the time measured will not be a true cold-cache
 > time.
 > 
 > Rik pointed out that "be_atomic" is a bit pointless since there is a
 > race on SMP anyway where pages can be added. However, it is there in
 > the existing code, so I added it for the new code as well. Does anyone
 > know why it's there?
 
this cset added it (and has a pretty explanatory commit msg)

	Dave

commit fc9a07e7bf1a76e710f5df017abb07628db1781d
Author: Andrew Morton <akpm@linux-foundation.org>
Date:   Sun Jul 15 23:38:14 2007 -0700

    invalidate_mapping_pages(): add cond_resched
    
    invalidate_mapping_pages() can sometimes take a long time (millions of pages
    to free).  Long enough for the softlockup detector to trigger.
    
    We used to have a cond_resched() in there but I took it out because the
    drop_caches code calls invalidate_mapping_pages() under inode_lock.
    
    The patch adds a nasty flag and puts the cond_resched() back.



-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-10-01  3:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 18:03 [PATCH] Add ability to dump mapped pages with /proc/sys/vm/drop_caches Soeren Sandmann
2007-10-01  3:36 ` Dave Jones [this message]
2007-10-02  8:44 ` Nick Piggin

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=20071001033605.GA11497@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandmann@daimi.au.dk \
    /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.