From mboxrd@z Thu Jan 1 00:00:00 1970 From: KOSAKI Motohiro Subject: Re: [PATCH 4/4] writeback: Reporting dirty thresholds in /proc/vmstat Date: Sun, 22 Aug 2010 19:27:54 +0900 (JST) Message-ID: <20100822192710.6018.A69D9226@jp.fujitsu.com> References: <1282296689-25618-5-git-send-email-mrubin@google.com> <20100820190603.6003.A69D9226@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Cc: kosaki.motohiro@jp.fujitsu.com, Michael Rubin , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, fengguang.wu@intel.com, jack@suse.cz, riel@redhat.com, akpm@linux-foundation.org, david@fromorbit.com, npiggin@kernel.dk, hch@lst.de, axboe@kernel.dk To: KOSAKI Motohiro Return-path: In-Reply-To: <20100820190603.6003.A69D9226@jp.fujitsu.com> Sender: owner-linux-mm@kvack.org List-Id: linux-fsdevel.vger.kernel.org > > 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 > > > > Signed-off-by: Michael Rubin > > Looks good to me. > Reviewed-by: KOSAKI Motohiro sorry, this is mistake. Wu pointed out this patch is unnecessary. Wu wrote: > 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? -- 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: email@kvack.org