From: Andrew Morton <akpm@linux-foundation.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: linux-mm@kvack.org, Dave Chinner <david@fromorbit.com>,
Hugh Dickins <hughd@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH RESEND] mm: trace filemap add and del
Date: Thu, 28 Feb 2013 13:25:49 -0800 [thread overview]
Message-ID: <20130228132549.b0bf04f7.akpm@linux-foundation.org> (raw)
In-Reply-To: <1362084420-3840-1-git-send-email-robert.jarzmik@free.fr>
On Thu, 28 Feb 2013 21:47:00 +0100
Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> Use the events API to trace filemap loading and unloading of file pieces
> into the page cache.
>
> This patch aims at tracing the eviction reload cycle of executable and
> shared libraries pages in a memory constrained environment.
>
> The typical usage is to spot a specific device and inode (for example
> /lib/libc.so) to see the eviction cycles, and find out if frequently used
> code is rather spread across many pages (bad) or coallesced (good).
>
> ...
>
> if (likely(!error)) {
> mapping->nrpages++;
> __inc_zone_page_state(page, NR_FILE_PAGES);
> + trace_mm_filemap_add_to_page_cache(page);
> spin_unlock_irq(&mapping->tree_lock);
> } else {
> page->mapping = NULL;
I don't see a need to do this under the spinlock. The page is locked
so nobody else will be fiddling with it. There would be a tiny
scalability gain from moving the tracepoint outside the locked region.
--
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>
next prev parent reply other threads:[~2013-02-28 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 20:47 [PATCH RESEND] mm: trace filemap add and del Robert Jarzmik
2013-02-28 21:25 ` Andrew Morton [this message]
2013-02-28 21:33 ` Steven Rostedt
2013-03-02 12:04 ` [PATCH RESEND v2] " Robert Jarzmik
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=20130228132549.b0bf04f7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=fweisbec@gmail.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=robert.jarzmik@free.fr \
--cc=rostedt@goodmis.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 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).