From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH 3/3] writeback: tracking subsystems causing writeback Date: Sat, 19 Jun 2010 10:17:01 +0200 Message-ID: <878w6bphc2.fsf@basil.nowhere.org> References: <1276907415-504-1-git-send-email-mrubin@google.com> <1276907415-504-4-git-send-email-mrubin@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, hch@lst.de, axboe@kernel.dk To: Michael Rubin Return-path: In-Reply-To: <1276907415-504-4-git-send-email-mrubin@google.com> (Michael Rubin's message of "Fri, 18 Jun 2010 17:30:15 -0700") Sender: owner-linux-mm@kvack.org List-Id: linux-fsdevel.vger.kernel.org Michael Rubin writes: > > # cat /sys/block/sda/bdi/writeback_stats > balance dirty pages 0 > balance dirty pages waiting 0 > periodic writeback 92024 > periodic writeback exited 0 > laptop periodic 0 > laptop or bg threshold 0 > free more memory 0 > try to free pages 271 > syc_sync 6 > sync filesystem 0 That exports a lot of kernel internals in /sys, presumably read by some applications. What happens with the applications if the kernel internals ever change? Will the application break? It would be bad to not be able to change the kernel because of such an interface. -Andi -- ak@linux.intel.com -- Speaking for myself only. -- 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