From: Michael Rubin <mrubin@google.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Cc: jack@suse.cz, akpm@linux-foundation.org, david@fromorbit.com,
hch@lst.de, axboe@kernel.dk, Michael Rubin <mrubin@google.com>
Subject: [PATCH 0/3] writeback visibility
Date: Fri, 18 Jun 2010 17:30:12 -0700 [thread overview]
Message-ID: <1276907415-504-1-git-send-email-mrubin@google.com> (raw)
Debugging writeback issues and tuning an application's writeback activity is
easier when the activity is visible. With large clusters, classifying
and root causing writeback problems has been a big headache. This patch
series contains a series of patches that our team has been using to start
getting a handle on writeback behaviour. These changes should be helpful
for single system maintainers also. It's still a big headache.
Once these changes are reviewed I will make sure the Documentation files
are updated, but I expect some back and forth first.
Michael Rubin (3):
writeback: Creating /sys/kernel/mm/writeback/writeback
writeback: per bdi monitoring
writeback: tracking subsystems causing writeback
drivers/base/node.c | 14 +++++
fs/buffer.c | 2 +-
fs/fs-writeback.c | 28 +++++++--
fs/nilfs2/segment.c | 4 +-
fs/sync.c | 2 +-
include/linux/backing-dev.h | 9 +++
include/linux/mmzone.h | 2 +
include/linux/writeback.h | 50 +++++++++++++++-
mm/backing-dev.c | 137 ++++++++++++++++++++++---------------------
mm/mm_init.c | 122 ++++++++++++++++++++++++++++++++++++++
mm/page-writeback.c | 18 ++++--
mm/vmscan.c | 3 +-
mm/vmstat.c | 2 +
13 files changed, 311 insertions(+), 82 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Michael Rubin <mrubin@google.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Cc: jack@suse.cz, akpm@linux-foundation.org, david@fromorbit.com,
hch@lst.de, axboe@kernel.dk, Michael Rubin <mrubin@google.com>
Subject: [PATCH 0/3] writeback visibility
Date: Fri, 18 Jun 2010 17:30:12 -0700 [thread overview]
Message-ID: <1276907415-504-1-git-send-email-mrubin@google.com> (raw)
Debugging writeback issues and tuning an application's writeback activity is
easier when the activity is visible. With large clusters, classifying
and root causing writeback problems has been a big headache. This patch
series contains a series of patches that our team has been using to start
getting a handle on writeback behaviour. These changes should be helpful
for single system maintainers also. It's still a big headache.
Once these changes are reviewed I will make sure the Documentation files
are updated, but I expect some back and forth first.
Michael Rubin (3):
writeback: Creating /sys/kernel/mm/writeback/writeback
writeback: per bdi monitoring
writeback: tracking subsystems causing writeback
drivers/base/node.c | 14 +++++
fs/buffer.c | 2 +-
fs/fs-writeback.c | 28 +++++++--
fs/nilfs2/segment.c | 4 +-
fs/sync.c | 2 +-
include/linux/backing-dev.h | 9 +++
include/linux/mmzone.h | 2 +
include/linux/writeback.h | 50 +++++++++++++++-
mm/backing-dev.c | 137 ++++++++++++++++++++++---------------------
mm/mm_init.c | 122 ++++++++++++++++++++++++++++++++++++++
mm/page-writeback.c | 18 ++++--
mm/vmscan.c | 3 +-
mm/vmstat.c | 2 +
13 files changed, 311 insertions(+), 82 deletions(-)
--
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 reply other threads:[~2010-06-19 0:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 0:30 Michael Rubin [this message]
2010-06-19 0:30 ` [PATCH 0/3] writeback visibility Michael Rubin
2010-06-19 0:30 ` [PATCH 1/3] writeback: Creating /sys/kernel/mm/writeback/writeback Michael Rubin
2010-06-19 0:30 ` Michael Rubin
2010-06-19 10:44 ` Christoph Hellwig
2010-06-19 10:44 ` Christoph Hellwig
2010-06-19 17:44 ` Michael Rubin
2010-06-19 17:44 ` Michael Rubin
2010-06-19 17:44 ` Michael Rubin
2010-06-19 0:30 ` [PATCH 2/3] writeback: per bdi monitoring Michael Rubin
2010-06-19 0:30 ` Michael Rubin
2010-06-19 0:30 ` [PATCH 3/3] writeback: tracking subsystems causing writeback Michael Rubin
2010-06-19 0:30 ` Michael Rubin
2010-06-19 8:17 ` Andi Kleen
2010-06-19 8:17 ` Andi Kleen
2010-06-19 17:49 ` Michael Rubin
2010-06-19 17:49 ` Michael Rubin
2010-06-19 20:23 ` Andi Kleen
2010-06-19 20:23 ` Andi Kleen
2010-06-20 23:10 ` [PATCH 0/3] writeback visibility Dave Chinner
2010-06-20 23:10 ` Dave Chinner
2010-06-21 17:09 ` Michael Rubin
2010-06-21 17:09 ` Michael Rubin
2010-06-24 0:02 ` Dave Chinner
2010-06-24 0:02 ` Dave Chinner
2010-06-24 0:02 ` Dave Chinner
2010-06-25 7:15 ` Michael Rubin
2010-06-25 7:15 ` Michael Rubin
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=1276907415-504-1-git-send-email-mrubin@google.com \
--to=mrubin@google.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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.