LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Balbir Singh <balbir@in.ibm.com> To: Andrew Morton <akpm@linux-foundation.org> Cc: Herbert Poetzl <herbert@13thfloor.at>, "Eric W. Biederman" <ebiederm@xmission.com>, containers@lists.osdl.org, linux-kernel@vger.kernel.org, Dave Hansen <hansendc@us.ibm.com> Subject: Re: Linux-VServer example results for sharing vs. separate mappings ... Date: Mon, 26 Mar 2007 08:06:07 +0530 [thread overview] Message-ID: <46073197.2020707@in.ibm.com> (raw) In-Reply-To: <20070325105109.b15c74ac.akpm@linux-foundation.org> Andrew Morton wrote: >> Don't we break the global LRU with this scheme? > > Sure, but that's deliberate! > > (And we don't have a global LRU - the LRUs are per-zone). > Yes, true. But if we use zones for containers and say we have 400 of them, with all of them under limit. When the system wants to reclaim memory, we might not end up reclaiming the best pages. Am I missing something? >>> b) Create a new memory abstraction, call it the "software zone", which >>> is mostly decoupled from the present "hardware zones". Most of the MM >>> is reworked to use "software zones". The "software zones" are >>> runtime-resizeable, and obtain their pages via some means from the >>> hardware zones. A container uses a software zone. >>> >> I think the problem would be figuring out where to allocate memory from? >> What happens if a software zone spans across many hardware zones? > > Yes, that would be the tricky part. But we generally don't care what > physical zone user pages come from, apart from NUMA optimisation. > >> The reclaim mechanism proposed *does not impact the non-container users*. > > Yup. Let's keep plugging away with Pavel's approach, see where it gets us. > Yes, we have some changes that we've made to the reclaim logic, we hope to integrate a page cache controller soon. We are also testing the patches. Hopefully soon enough, they'll be in a good state and we can request you to merge the containers and the rss limit (plus page cache) controller soon. -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL
next prev parent reply other threads:[~2007-03-26 2:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-23 19:30 Linux-VServer example results for sharing vs. separate mappings Herbert Poetzl 2007-03-24 5:42 ` Andrew Morton 2007-03-24 18:38 ` Herbert Poetzl 2007-03-24 20:19 ` Andrew Morton 2007-03-25 2:21 ` Herbert Poetzl 2007-03-25 4:29 ` Andrew Morton 2007-03-25 14:40 ` Herbert Poetzl 2007-03-28 1:22 ` Ethan Solomita 2007-03-25 9:50 ` Balbir Singh 2007-03-25 18:51 ` Andrew Morton 2007-03-26 2:36 ` Balbir Singh [this message] 2007-03-26 5:26 ` Andrew Morton 2007-03-26 6:05 ` Balbir Singh 2007-03-26 9:26 ` [Devel] " Kirill Korotaev [not found] <81XMo-Fl-19@gated-at.bofh.it> [not found] ` <827iC-6DZ-7@gated-at.bofh.it> [not found] ` <82jjS-89s-11@gated-at.bofh.it> [not found] ` <82l2j-2lv-11@gated-at.bofh.it> [not found] ` <82qEC-2yM-9@gated-at.bofh.it> [not found] ` <83v9d-3kf-1@gated-at.bofh.it> 2007-03-29 7:24 ` Bodo Eggert
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=46073197.2020707@in.ibm.com \ --to=balbir@in.ibm.com \ --cc=akpm@linux-foundation.org \ --cc=containers@lists.osdl.org \ --cc=ebiederm@xmission.com \ --cc=hansendc@us.ibm.com \ --cc=herbert@13thfloor.at \ --cc=linux-kernel@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).