linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCHv6 14/15] writeback: add new tracepoints
Date: Sun, 25 Jul 2010 14:29:24 +0300	[thread overview]
Message-ID: <1280057365-10297-15-git-send-email-dedekind1@gmail.com> (raw)
In-Reply-To: <1280057365-10297-1-git-send-email-dedekind1@gmail.com>

From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>

Add 2 new trace points to the periodic write-back wake up case, just like we do
in the 'bdi_queue_work()' function. Namely, introduce:

1. trace_writeback_wake_thread(bdi)
2. trace_writeback_wake_forker_thread(bdi)

The first event is triggered every time we wake up a bdi thread to start
periodic background write-out. The second event is triggered only when the bdi
thread does not exist and should be created by the forker thread.

This patch was suggested by Dave Chinner and Christoph Hellwig.

Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
---
 include/trace/events/writeback.h |    2 ++
 mm/backing-dev.c                 |    2 ++
 2 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/include/trace/events/writeback.h b/include/trace/events/writeback.h
index 84ab72d..f345f66 100644
--- a/include/trace/events/writeback.h
+++ b/include/trace/events/writeback.h
@@ -81,6 +81,8 @@ DEFINE_EVENT(writeback_class, name, \
 	TP_ARGS(bdi))
 
 DEFINE_WRITEBACK_EVENT(writeback_nowork);
+DEFINE_WRITEBACK_EVENT(writeback_wake_thread);
+DEFINE_WRITEBACK_EVENT(writeback_wake_forker_thread);
 DEFINE_WRITEBACK_EVENT(writeback_bdi_register);
 DEFINE_WRITEBACK_EVENT(writeback_bdi_unregister);
 DEFINE_WRITEBACK_EVENT(writeback_thread_start);
diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index 9989083..9008c4e 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -310,6 +310,7 @@ static void wakeup_timer_fn(unsigned long data)
 
 	spin_lock_bh(&bdi->wb_lock);
 	if (bdi->wb.task) {
+		trace_writeback_wake_thread(bdi);
 		wake_up_process(bdi->wb.task);
 	} else {
 		/*
@@ -317,6 +318,7 @@ static void wakeup_timer_fn(unsigned long data)
 		 * In this case we have to wake-up the forker thread which
 		 * should create and run the bdi thread.
 		 */
+		trace_writeback_wake_forker_thread(bdi);
 		wake_up_process(default_backing_dev_info.wb.task);
 	}
 	spin_unlock_bh(&bdi->wb_lock);
-- 
1.7.1.1


  parent reply	other threads:[~2010-07-25 11:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25 11:29 [PATCHv6 00/15] kill unnecessary bdi wakeups + cleanups Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 01/15] writeback: harmonize writeback threads naming Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 02/15] writeback: fix possible race when creating bdi threads Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 03/15] writeback: do not lose wake-ups in the forker thread - 1 Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 04/15] writeback: do not lose wake-ups in the forker thread - 2 Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 05/15] writeback: do not lose wake-ups in bdi threads Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 06/15] writeback: simplify bdi code a little Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 07/15] writeback: do not remove bdi from bdi_list Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 08/15] writeback: move last_active to bdi Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 09/15] writeback: restructure bdi forker loop a little Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 10/15] writeback: move bdi threads exiting logic to the forker thread Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 11/15] writeback: prevent unnecessary bdi threads wakeups Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 12/15] writeback: optimize periodic bdi thread wakeups Artem Bityutskiy
2010-07-25 11:29 ` [PATCHv6 13/15] writeback: remove unnecessary init_timer call Artem Bityutskiy
2010-07-25 11:29 ` Artem Bityutskiy [this message]
2010-07-25 11:29 ` [PATCHv6 15/15] writeback: cleanup bdi_register Artem Bityutskiy
2010-08-03  4:44 ` [PATCHv6 00/15] kill unnecessary bdi wakeups + cleanups Artem Bityutskiy
2010-08-03 12:27 ` Jens Axboe
2010-08-03 12:37   ` Artem Bityutskiy
2010-08-03 12:47     ` Jens Axboe
2010-08-04 11:34       ` Jens Axboe
2010-08-05  9:35         ` Artem Bityutskiy
2010-08-03 14:11   ` Artem Bityutskiy

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=1280057365-10297-15-git-send-email-dedekind1@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).