From: Rik van Riel <riel@redhat.com>
To: Michael Rubin <mrubin@google.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, jack@suse.cz, akpm@linux-foundation.org,
david@fromorbit.com, npiggin@suse.de, hch@lst.de,
axboe@kernel.dk
Subject: Re: [PATCH 0/3] writeback: kernel visibility
Date: Thu, 19 Aug 2010 18:11:33 -0400 [thread overview]
Message-ID: <4C6DAC15.7040004@redhat.com> (raw)
In-Reply-To: <1282251447-16937-1-git-send-email-mrubin@google.com>
On 08/19/2010 04:57 PM, Michael Rubin wrote:
> Patch #1 sets up some helper functions for accounting.
>
> Patch #2 adds writeback visibility in /proc/sys/vm.
>
> To help developers and applications gain visibility into writeback
> behaviour adding two read-only sysctl files into /proc/sys/vm.
> These files allow user apps to understand writeback behaviour over time
> and learn how it is impacting their performance.
>
> # cat /proc/sys/vm/pages_dirtied
> 3747
> # cat /proc/sys/vm/pages_entered_writeback
> 3618
Would it be better to have these values in /proc/vmstat
and /proc/zoneinfo ?
I don't really see why they need to be in /proc/sys
at all...
--
All rights reversed
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Michael Rubin <mrubin@google.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, jack@suse.cz, akpm@linux-foundation.org,
david@fromorbit.com, npiggin@suse.de, hch@lst.de,
axboe@kernel.dk
Subject: Re: [PATCH 0/3] writeback: kernel visibility
Date: Thu, 19 Aug 2010 18:11:33 -0400 [thread overview]
Message-ID: <4C6DAC15.7040004@redhat.com> (raw)
In-Reply-To: <1282251447-16937-1-git-send-email-mrubin@google.com>
On 08/19/2010 04:57 PM, Michael Rubin wrote:
> Patch #1 sets up some helper functions for accounting.
>
> Patch #2 adds writeback visibility in /proc/sys/vm.
>
> To help developers and applications gain visibility into writeback
> behaviour adding two read-only sysctl files into /proc/sys/vm.
> These files allow user apps to understand writeback behaviour over time
> and learn how it is impacting their performance.
>
> # cat /proc/sys/vm/pages_dirtied
> 3747
> # cat /proc/sys/vm/pages_entered_writeback
> 3618
Would it be better to have these values in /proc/vmstat
and /proc/zoneinfo ?
I don't really see why they need to be in /proc/sys
at all...
--
All rights reversed
--
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:[~2010-08-19 22:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 20:57 [PATCH 0/3] writeback: kernel visibility Michael Rubin
2010-08-19 20:57 ` Michael Rubin
2010-08-19 20:57 ` [PATCH 1/3] mm: helper functions for dirty and writeback accounting Michael Rubin
2010-08-19 20:57 ` Michael Rubin
2010-08-20 2:34 ` Wu Fengguang
2010-08-20 2:34 ` Wu Fengguang
2010-08-20 8:19 ` Michael Rubin
2010-08-20 8:19 ` Michael Rubin
2010-08-19 20:57 ` [PATCH 2/3] writeback: Adding pages_dirtied and pages_entered_writeback Michael Rubin
2010-08-19 20:57 ` Michael Rubin
2010-08-20 2:51 ` Wu Fengguang
2010-08-20 2:51 ` Wu Fengguang
2010-08-20 6:54 ` Wu Fengguang
2010-08-20 6:54 ` Wu Fengguang
2010-08-20 8:16 ` Michael Rubin
2010-08-20 8:16 ` Michael Rubin
2010-08-20 8:43 ` Wu Fengguang
2010-08-20 8:43 ` Wu Fengguang
2010-08-20 8:43 ` Wu Fengguang
2010-08-19 20:57 ` [PATCH 3/3] writeback: Reporting dirty thresholds in /proc/vmstat Michael Rubin
2010-08-19 20:57 ` Michael Rubin
2010-08-20 3:16 ` Wu Fengguang
2010-08-20 3:16 ` Wu Fengguang
2010-08-20 8:18 ` Michael Rubin
2010-08-20 8:18 ` Michael Rubin
2010-08-19 22:11 ` Rik van Riel [this message]
2010-08-19 22:11 ` [PATCH 0/3] writeback: kernel visibility Rik van Riel
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=4C6DAC15.7040004@redhat.com \
--to=riel@redhat.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 \
--cc=mrubin@google.com \
--cc=npiggin@suse.de \
/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.