From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wu Fengguang Subject: [LSF/MM][ATTEND] readahead and writeback Date: Sun, 5 Feb 2012 23:00:59 +0800 Message-ID: <20120205150059.GA32739@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linux Memory Management List , linux-fsdevel@vger.kernel.org To: lsf-pc@lists.linux-foundation.org Return-path: Received: from mga14.intel.com ([143.182.124.37]:9872 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754182Ab2BEPLP (ORCPT ); Sun, 5 Feb 2012 10:11:15 -0500 Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: I would like to attend to participate in the readahead and writeback discussions. My questions are - readahead size and alignment, hope that we can reach some general agreements on the policy stuff - async write I/O bandwidth controller, will it be a good complement feature to the current blk-cgroup I/O controller? Each seem to have its own strong areas and weak points. - per-memcg dirty pages control, to be frank, it's non-trivial to implement and I'm not sure it will perform well in some cases. Before following that direction, I'm curious whether the much more simple scheme of moving dirty pages to the global LRU can magically satisfy the main user demands. Thanks, Fengguang