Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753640Ab1BVVFt (ORCPT ); Tue, 22 Feb 2011 16:05:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:14166 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752276Ab1BVVFr (ORCPT ); Tue, 22 Feb 2011 16:05:47 -0500 Date: Tue, 22 Feb 2011 16:00:30 -0500 From: Vivek Goyal To: Andrea Righi Cc: Balbir Singh , Daisuke Nishimura , KAMEZAWA Hiroyuki , Greg Thelen , Wu Fengguang , Gui Jianfeng , Ryo Tsuruta , Hirokazu Takahashi , Jens Axboe , Andrew Morton , containers@lists.linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 4/5] blk-throttle: track buffered and anonymous pages Message-ID: <20110222210030.GI28269@redhat.com> References: <1298394776-9957-1-git-send-email-arighi@develer.com> <1298394776-9957-5-git-send-email-arighi@develer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1298394776-9957-5-git-send-email-arighi@develer.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3302 Lines: 95 On Tue, Feb 22, 2011 at 06:12:55PM +0100, Andrea Righi wrote: > Add the tracking of buffered (writeback) and anonymous pages. > > Dirty pages in the page cache can be processed asynchronously by the > per-bdi flusher kernel threads or by any other thread in the system, > according to the writeback policy. > > For this reason the real writes to the underlying block devices may > occur in a different IO context respect to the task that originally > generated the dirty pages involved in the IO operation. This makes > the tracking and throttling of writeback IO more complicate respect to > the synchronous IO from the blkio controller's point of view. > > The idea is to save the cgroup owner of each anonymous page and dirty > page in page cache. A page is associated to a cgroup the first time it > is dirtied in memory (for file cache pages) or when it is set as > swap-backed (for anonymous pages). This information is stored using the > page_cgroup functionality. > > Then, at the block layer, it is possible to retrieve the throttle group > looking at the bio_page(bio). If the page was not explicitly associated > to any cgroup the IO operation is charged to the current task/cgroup, as > it was done by the previous implementation. > > Signed-off-by: Andrea Righi > --- > block/blk-throttle.c | 87 +++++++++++++++++++++++++++++++++++++++++++++++- > include/linux/blkdev.h | 26 ++++++++++++++- > 2 files changed, 111 insertions(+), 2 deletions(-) > > diff --git a/block/blk-throttle.c b/block/blk-throttle.c > index 9ad3d1e..a50ee04 100644 > --- a/block/blk-throttle.c > +++ b/block/blk-throttle.c > @@ -8,6 +8,10 @@ > #include > #include > #include > +#include > +#include > +#include > +#include > #include > #include > > @@ -221,6 +225,85 @@ done: > return tg; > } > > +static inline bool is_kernel_io(void) > +{ > + return !!(current->flags & (PF_KTHREAD | PF_KSWAPD | PF_MEMALLOC)); > +} > + > +static int throtl_set_page_owner(struct page *page, struct mm_struct *mm) > +{ > + struct blkio_cgroup *blkcg; > + unsigned short id = 0; > + > + if (blkio_cgroup_disabled()) > + return 0; > + if (!mm) > + goto out; > + rcu_read_lock(); > + blkcg = task_to_blkio_cgroup(rcu_dereference(mm->owner)); > + if (likely(blkcg)) > + id = css_id(&blkcg->css); > + rcu_read_unlock(); > +out: > + return page_cgroup_set_owner(page, id); > +} > + > +int blk_throtl_set_anonpage_owner(struct page *page, struct mm_struct *mm) > +{ > + return throtl_set_page_owner(page, mm); > +} > +EXPORT_SYMBOL(blk_throtl_set_anonpage_owner); > + > +int blk_throtl_set_filepage_owner(struct page *page, struct mm_struct *mm) > +{ > + if (is_kernel_io() || !page_is_file_cache(page)) > + return 0; > + return throtl_set_page_owner(page, mm); > +} > +EXPORT_SYMBOL(blk_throtl_set_filepage_owner); Why are we exporting all these symbols? Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/