Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753443Ab1CKSrf (ORCPT ); Fri, 11 Mar 2011 13:47:35 -0500 Received: from smtp-out.google.com ([74.125.121.67]:30733 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753495Ab1CKSra (ORCPT ); Fri, 11 Mar 2011 13:47:30 -0500 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=from:to:cc:subject:date:message-id:x-mailer:in-reply-to:references; b=T6tZJFa/gTPmc4A9UNxsGT8xHPoResWkf/VkTs7nqWf/xh0punKV9BAuI1EOz5gYu dvcoZkwRqemAF6s4qa1XA== From: Greg Thelen To: Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, containers@lists.osdl.org, linux-fsdevel@vger.kernel.org, Andrea Righi , Balbir Singh , KAMEZAWA Hiroyuki , Daisuke Nishimura , Minchan Kim , Johannes Weiner , Ciju Rajan K , David Rientjes , Wu Fengguang , Chad Talbott , Justin TerAvest , Vivek Goyal , Greg Thelen Subject: [PATCH v6 8/9] memcg: check memcg dirty limits in page writeback Date: Fri, 11 Mar 2011 10:43:30 -0800 Message-Id: <1299869011-26152-9-git-send-email-gthelen@google.com> X-Mailer: git-send-email 1.7.3.1 In-Reply-To: <1299869011-26152-1-git-send-email-gthelen@google.com> References: <1299869011-26152-1-git-send-email-gthelen@google.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5620 Lines: 151 If the current process is in a non-root memcg, then balance_dirty_pages() will consider the memcg dirty limits as well as the system-wide limits. This allows different cgroups to have distinct dirty limits which trigger direct and background writeback at different levels. If called with a mem_cgroup, then throttle_vm_writeout() queries the given cgroup for its dirty memory usage limits. Signed-off-by: Andrea Righi Signed-off-by: Greg Thelen Acked-by: KAMEZAWA Hiroyuki Acked-by: Wu Fengguang --- Changelog since v5: - Simplified this change by using mem_cgroup_balance_dirty_pages() rather than cramming the somewhat different logic into balance_dirty_pages(). This means the global (non-memcg) dirty limits are not passed around in the struct dirty_info, so there's less change to existing code. Changelog since v4: - Added missing 'struct mem_cgroup' forward declaration in writeback.h. - Made throttle_vm_writeout() memcg aware. - Removed previously added dirty_writeback_pages() which is no longer needed. - Added logic to balance_dirty_pages() to throttle if over foreground memcg limit. Changelog since v3: - Leave determine_dirtyable_memory() static. v3 made is non-static. - balance_dirty_pages() now considers both system and memcg dirty limits and usage data. This data is retrieved with global_dirty_info() and memcg_dirty_info(). include/linux/writeback.h | 3 ++- mm/page-writeback.c | 34 ++++++++++++++++++++++++++++------ mm/vmscan.c | 2 +- 3 files changed, 31 insertions(+), 8 deletions(-) diff --git a/include/linux/writeback.h b/include/linux/writeback.h index 0ead399..a45d895 100644 --- a/include/linux/writeback.h +++ b/include/linux/writeback.h @@ -8,6 +8,7 @@ #include struct backing_dev_info; +struct mem_cgroup; extern spinlock_t inode_lock; @@ -92,7 +93,7 @@ void laptop_mode_timer_fn(unsigned long data); #else static inline void laptop_sync_completion(void) { } #endif -void throttle_vm_writeout(gfp_t gfp_mask); +void throttle_vm_writeout(gfp_t gfp_mask, struct mem_cgroup *mem_cgroup); /* These are exported to sysctl. */ extern int dirty_background_ratio; diff --git a/mm/page-writeback.c b/mm/page-writeback.c index d8005b0..f6a8dd6 100644 --- a/mm/page-writeback.c +++ b/mm/page-writeback.c @@ -473,7 +473,8 @@ unsigned long bdi_dirty_limit(struct backing_dev_info *bdi, unsigned long dirty) * data. It looks at the number of dirty pages in the machine and will force * the caller to perform writeback if the system is over `vm_dirty_ratio'. * If we're over `background_thresh' then the writeback threads are woken to - * perform some writeout. + * perform some writeout. The current task may have per-memcg dirty + * limits, which are also checked. */ static void balance_dirty_pages(struct address_space *mapping, unsigned long write_chunk) @@ -488,6 +489,8 @@ static void balance_dirty_pages(struct address_space *mapping, bool dirty_exceeded = false; struct backing_dev_info *bdi = mapping->backing_dev_info; + mem_cgroup_balance_dirty_pages(mapping, write_chunk); + for (;;) { struct writeback_control wbc = { .sync_mode = WB_SYNC_NONE, @@ -651,23 +654,42 @@ void balance_dirty_pages_ratelimited_nr(struct address_space *mapping, } EXPORT_SYMBOL(balance_dirty_pages_ratelimited_nr); -void throttle_vm_writeout(gfp_t gfp_mask) +/* + * Throttle the current task if it is near dirty memory usage limits. Both + * global dirty memory limits and (if @mem_cgroup is given) per-cgroup dirty + * memory limits are checked. + * + * If near limits, then wait for usage to drop. Dirty usage should drop because + * dirty producers should have used balance_dirty_pages(), which would have + * scheduled writeback. + */ +void throttle_vm_writeout(gfp_t gfp_mask, struct mem_cgroup *mem_cgroup) { unsigned long background_thresh; unsigned long dirty_thresh; + struct dirty_info memcg_info; + bool do_memcg; for ( ; ; ) { global_dirty_limits(&background_thresh, &dirty_thresh); + do_memcg = mem_cgroup && mem_cgroup_hierarchical_dirty_info( + determine_dirtyable_memory(), true, mem_cgroup, + &memcg_info); /* * Boost the allowable dirty threshold a bit for page * allocators so they don't get DoS'ed by heavy writers */ dirty_thresh += dirty_thresh / 10; /* wheeee... */ - - if (global_page_state(NR_UNSTABLE_NFS) + - global_page_state(NR_WRITEBACK) <= dirty_thresh) - break; + if (do_memcg) + memcg_info.dirty_thresh += memcg_info.dirty_thresh / 10; + + if ((global_page_state(NR_UNSTABLE_NFS) + + global_page_state(NR_WRITEBACK) <= dirty_thresh) && + (!do_memcg || + (memcg_info.nr_unstable_nfs + + memcg_info.nr_writeback <= memcg_info.dirty_thresh))) + break; congestion_wait(BLK_RW_ASYNC, HZ/10); /* diff --git a/mm/vmscan.c b/mm/vmscan.c index 060e4c1..035d2ea 100644 --- a/mm/vmscan.c +++ b/mm/vmscan.c @@ -1939,7 +1939,7 @@ restart: sc->nr_scanned - nr_scanned, sc)) goto restart; - throttle_vm_writeout(sc->gfp_mask); + throttle_vm_writeout(sc->gfp_mask, sc->mem_cgroup); } /* -- 1.7.3.1 -- 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/