[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100821054808.GA29869@localhost>
Date: Sat, 21 Aug 2010 13:48:08 +0800
From: Wu Fengguang <fengguang.wu@...el.com>
To: Michael Rubin <mrubin@...gle.com>
Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"jack@...e.cz" <jack@...e.cz>, "riel@...hat.com" <riel@...hat.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"david@...morbit.com" <david@...morbit.com>,
"npiggin@...nel.dk" <npiggin@...nel.dk>, "hch@....de" <hch@....de>,
"axboe@...nel.dk" <axboe@...nel.dk>
Subject: Re: [PATCH 4/4] writeback: Reporting dirty thresholds in
/proc/vmstat
On Fri, Aug 20, 2010 at 05:31:29PM +0800, Michael Rubin wrote:
> The kernel already exposes the user desired thresholds in /proc/sys/vm
> with dirty_background_ratio and background_ratio. But the kernel may
> alter the number requested without giving the user any indication that
> is the case.
>
> Knowing the actual ratios the kernel is honoring can help app developers
> understand how their buffered IO will be sent to the disk.
>
> $ grep threshold /proc/vmstat
> nr_dirty_threshold 409111
> nr_dirty_background_threshold 818223
I realized that the dirty thresholds has already been exported here:
$ grep Thresh /debug/bdi/8:0/stats
BdiDirtyThresh: 381000 kB
DirtyThresh: 1719076 kB
BackgroundThresh: 859536 kB
So why not use that interface directly?
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists