On 2016/02/19 14:37, Ian Kent wrote:
On Fri, 2016-02-19 at 12:08 +0900, Kamezawa Hiroyuki wrote:
On 2016/02/19 5:45, Eric W. Biederman wrote:
Personally I am a fan of the don't be clever and capture a kernel
thread
approach as it is very easy to see you what if any exploitation
opportunities
On 2016/02/19 5:45, Eric W. Biederman wrote:
> Personally I am a fan of the don't be clever and capture a kernel thread
> approach as it is very easy to see you what if any exploitation
> opportunities there are. The justifications for something more clever
> is trickier. Of course we do
On 2016/02/18 11:57, Eric W. Biederman wrote:
>
> Ccing The containers list because a related discussion is happening there
> and somehow this thread has never made it there.
>
> Ian Kent writes:
>
>> On Mon, 2013-11-18 at 18:28 +0100, Oleg Nesterov wrote:
>>> On 11/15, Eric
: Christoph Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Tejun Heo t...@kernel.org
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
...@parallels.com
Tested-by: Greg Thelen gthe...@google.com
Acked-by: Michal Hocko mho...@suse.cz
CC: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Tejun Heo t...@kernel.org
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
(2012/10/08 19:06), Glauber Costa wrote:
Signed-off-by: Glauber Costa glom...@parallels.com
---
Documentation/cgroups/memory.txt | 55
+++-
1 file changed, 54 insertions(+), 1 deletion(-)
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
(2012/10/12 18:13), Glauber Costa wrote:
On 10/12/2012 12:57 PM, Michal Hocko wrote:
On Fri 12-10-12 12:44:57, Glauber Costa wrote:
On 10/12/2012 12:39 PM, Michal Hocko wrote:
On Fri 12-10-12 11:45:46, Glauber Costa wrote:
On 10/11/2012 04:42 PM, Michal Hocko wrote:
On Mon 08-10-12
this value.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Michal Hocko mho...@suse.cz
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
---
Documentation/cgroups/resource_counter.txt | 7
]
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Christoph Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
OK, I
.
It is a lot simpler just to do static_key_slow_inc() on every child
that is accounted.
[ v4: adapted this patch to the changes in kmem_accounted ]
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Christoph Lameter c...@linux.com
CC
sure not to do it if
__GFP_NORETRY.
[v4: fixed nr pages calculation pointed out by Christoph Lameter ]
Signed-off-by: Suleiman Souhlal sulei...@google.com
Signed-off-by: Glauber Costa glom...@parallels.com
Reviewed-by: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
Acked-by: Michal Hocko
(2012/08/13 17:28), Glauber Costa wrote:
+ * Needs to be called after memcg_kmem_new_page, regardless of success or
+ * failure of the allocation. if @page is NULL, this function will revert
the
+ * charges. Otherwise, it will commit the memcg given by @handle to the
+ * corresponding
(2012/08/13 17:36), Glauber Costa wrote:
On 08/10/2012 09:02 PM, Kamezawa Hiroyuki wrote:
(2012/08/09 22:01), Glauber Costa wrote:
This patch adds the basic infrastructure for the accounting of the slab
caches. To control that, the following files are created:
* memory.kmem.usage_in_bytes
(2012/08/11 0:42), Michal Hocko wrote:
On Thu 09-08-12 17:01:10, Glauber Costa wrote:
[...]
@@ -2317,18 +2318,18 @@ static int mem_cgroup_do_charge(struct mem_cgroup
*memcg, gfp_t gfp_mask,
} else
mem_over_limit = mem_cgroup_from_res_counter(fail_res, res);
/*
-
...@parallels.com
CC: Michal Hocko mho...@suse.cz
CC: Johannes Weiner han...@cmpxchg.org
Reviewed-by: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
Could you add a patch for documentation of this new interface and a text
explaining the behavior of kmem_accounting ?
Hm, my concern is the difference
Costa glom...@parallels.com
CC: Christoph Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
CC: Rik van Riel r
: Christoph Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
---
include/linux/memcontrol.h | 79 +++
mm/memcontrol.c| 185
of
__free_accounted_pages() and free_accounted_pages().
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Christoph Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
---
mm/memcontrol.c | 88
Costa glom...@parallels.com
Acked-by: Frederic Weisbecker fweis...@redhat.com
CC: Christoph Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman
(2012/08/11 2:28), Michal Hocko wrote:
On Sat 11-08-12 01:49:25, KAMEZAWA Hiroyuki wrote:
(2012/08/11 0:42), Michal Hocko wrote:
On Thu 09-08-12 17:01:10, Glauber Costa wrote:
[...]
@@ -2317,18 +2318,18 @@ static int mem_cgroup_do_charge(struct mem_cgroup
*memcg, gfp_t gfp_mask
(2012/07/12 6:41), Kir Kolyshkin wrote:
Gentlemen,
We are organizing containers mini-summit during next Linux Plumbers (San Diego,
August 29-31).
The idea is to gather and discuss everything relevant to namespaces, cgroups,
resource management,
checkpoint-restore and so on.
We are trying to
Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
---
mm/memcontrol.c | 10 +-
1 file changed, 9
: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
Hm.
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
___
Devel mailing list
Devel@openvz.org
https://openvz.org/mailman/listinfo/devel
(2012/06/26 13:57), David Rientjes wrote:
On Mon, 25 Jun 2012, Glauber Costa wrote:
diff --git a/include/linux/thread_info.h b/include/linux/thread_info.h
index ccc1899..914ec07 100644
--- a/include/linux/thread_info.h
+++ b/include/linux/thread_info.h
@@ -61,6 +61,12 @@ extern long
...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
(2012/06/20 17:59), Glauber Costa wrote:
On 06/19/2012 12:54 PM, Glauber Costa wrote:
On 06/19/2012 12:35 PM, Glauber Costa wrote:
On 06/19/2012 04:16 AM, Kamezawa Hiroyuki wrote:
(2012/06/18 21:43), Glauber Costa wrote:
On 06/18/2012 04:37 PM, Kamezawa Hiroyuki wrote:
(2012/06/18 19:28
(2012/06/20 17:40), Glauber Costa wrote:
On 06/20/2012 11:32 AM, Pekka Enberg wrote:
Maybe Pekka can merge the current -mm with his tree?
I first want to have a stable base from Christoph's common slab series
before I am comfortable with going forward with the memcg parts.
Feel free to push
first as simple cleanu up and
to reduce patch stack on your side ?
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
---
mm/memcontrol.c | 24 +---
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index e3b528e
(2012/06/18 19:27), Glauber Costa wrote:
Hello All,
This is my new take for the memcg kmem accounting. This should merge
all of the previous comments from you guys, specially concerning the big churn
inside the allocators themselves.
My focus in this new round was to keep the changes in
...@suse.cz
CC: Kamezawa Hiroyukikamezawa.hir...@jp.fujitsu.com
CC: Johannes Weinerhan...@cmpxchg.org
CC: Suleiman Souhlalsulei...@google.com
I'm ok with this approach.
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
___
Devel mailing list
(2012/06/18 19:28), Glauber Costa wrote:
We can use jump labels to patch the code in or out
when not used.
Because the assignment: memcg-kmem_accounted = true
is done after the jump labels increment, we guarantee
that the root memcg will always be selected until
all call sites are patched
(2012/06/18 19:28), Glauber Costa wrote:
The current memcg slab cache management fails to present satisfatory
hierarchical
behavior in the following scenario:
- /cgroups/memory/A/B/C
* kmem limit set at A
* A and B empty taskwise
* bash in C does find /
Because kmem_accounted is a
(2012/06/18 21:10), Glauber Costa wrote:
On 06/18/2012 04:07 PM, Kamezawa Hiroyuki wrote:
(2012/06/18 19:27), Glauber Costa wrote:
Right now we free struct memcg with kfree right after a
rcu grace period, but defer it if we need to use vfree() to get
rid of that memory area. We do
(2012/06/18 21:43), Glauber Costa wrote:
On 06/18/2012 04:37 PM, Kamezawa Hiroyuki wrote:
(2012/06/18 19:28), Glauber Costa wrote:
The current memcg slab cache management fails to present satisfatory
hierarchical
behavior in the following scenario:
- /cgroups/memory/A/B/C
* kmem limit
(2012/06/07 23:00), Frederic Weisbecker wrote:
On Thu, Jun 07, 2012 at 02:53:07PM +0400, Glauber Costa wrote:
On 06/07/2012 02:26 PM, Frederic Weisbecker wrote:
On Fri, May 25, 2012 at 05:03:20PM +0400, Glauber Costa wrote:
Hello All,
This is my new take for the memcg kmem accounting. This
(2012/05/17 18:52), Glauber Costa wrote:
On 05/17/2012 09:37 AM, Andrew Morton wrote:
If that happens, locking in static_key_slow_inc will prevent any damage.
My previous version had explicit code to prevent that, but we were
pointed out that this is already part of the static_key
(2012/05/17 19:22), Glauber Costa wrote:
On 05/17/2012 02:18 PM, KAMEZAWA Hiroyuki wrote:
(2012/05/17 18:52), Glauber Costa wrote:
On 05/17/2012 09:37 AM, Andrew Morton wrote:
If that happens, locking in static_key_slow_inc will prevent any
damage.
My previous version had explicit
(2012/05/16 15:19), Glauber Costa wrote:
On 05/15/2012 06:46 AM, KAMEZAWA Hiroyuki wrote:
(2012/05/12 2:44), Glauber Costa wrote:
This patch creates a mechanism that skip memcg allocations during
certain pieces of our core code. It basically works in the same way
as preempt_disable
(2012/05/16 15:42), Glauber Costa wrote:
On 05/15/2012 06:57 AM, KAMEZAWA Hiroyuki wrote:
+#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM
+int memcg_charge_kmem(struct mem_cgroup *memcg, gfp_t gfp, s64 delta)
+{
+ struct res_counter *fail_res;
+ struct mem_cgroup *_memcg;
+ int may_oom, ret
(2012/05/16 16:04), Glauber Costa wrote:
On 05/16/2012 10:03 AM, Glauber Costa wrote:
BTW, what is the relationship between 1/2 and 2/2 ?
Can't do jump label patching inside an interrupt handler. They need to
happen when we free the structure, and I was about to add a worker
myself when I
(2012/05/16 17:25), Glauber Costa wrote:
On 05/16/2012 12:18 PM, KAMEZAWA Hiroyuki wrote:
If at this point the memcg hits a NOFAIL allocation worth 2 pages, by
the method I am using, the memcg will be at 4M + 4k after the
allocation. Charging it to the root memcg will leave it at 4M - 4k
(2012/05/17 6:13), Andrew Morton wrote:
On Fri, 11 May 2012 17:11:17 -0300
Glauber Costa glom...@parallels.com wrote:
We call the destroy function when a cgroup starts to be removed,
such as by a rmdir event.
However, because of our reference counters, some objects are still
inflight.
...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
The concept seems okay to me but...
---
include/linux/sched.h |1 +
mm/memcontrol.c | 25 +
2 files changed, 26
...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
---
include/linux/memcontrol.h | 67
init/Kconfig |2 +-
mm/memcontrol.c| 379
(2012/05/12 2:44), Glauber Costa wrote:
From: Frederic Weisbecker fweis...@gmail.com
Moving a task from a cgroup to another may require to substract its
resource charge from the old cgroup and add it to the new one.
For this to happen, the uncharge/charge propagation can just stop when we
the jump_label_mutex)
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Tejun Heo t...@kernel.org
CC: Li Zefan lize...@huawei.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Michal Hocko mho...@suse.cz
I think we'll need to revisit
free_work ]
[v5: got rid of tcp_limit_mutex, now in the static_key interface ]
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Tejun Heo t...@kernel.org
CC: Li Zefan lize...@huawei.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Michal
combination instead of just an atomic should not kill
us.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Tejun Heo t...@kernel.org
CC: Li Zefan lize...@huawei.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Michal Hocko mho...@suse.cz
(2012/04/25 23:29), Glauber Costa wrote:
On 04/24/2012 10:44 PM, KAMEZAWA Hiroyuki wrote:
(2012/04/23 8:53), Glauber Costa wrote:
Some allocations need to be accounted to the root memcg regardless
of their context. One trivial example, is the allocations we do
during the memcg slab cache
(2012/04/24 20:41), Glauber Costa wrote:
On 04/23/2012 11:40 PM, KAMEZAWA Hiroyuki wrote:
(2012/04/24 4:37), Glauber Costa wrote:
We call the destroy function when a cgroup starts to be removed,
such as by a rmdir event.
However, because of our reference counters, some objects are still
(2012/04/21 6:57), Glauber Costa wrote:
From: Suleiman Souhlal ssouh...@freebsd.org
Signed-off-by: Suleiman Souhlal sulei...@google.com
ok, should work enough.
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
___
Devel mailing list
to
COSTLY_ORDER (as page_alloc.c does), stay safe with a cond_resched(),
and make sure not to do it if __GFP_NORETRY.
Signed-off-by: Suleiman Souhlal sulei...@google.com
Hmm, maybe ok.
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
---
mm/memcontrol.c | 18
(2012/04/21 6:57), Glauber Costa wrote:
This is just a cleanup patch for clarity of expression.
In earlier submissions, people asked it to be in a separate
patch, so here it is.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki
(2012/04/21 6:57), Glauber Costa wrote:
Since we will succeed with the allocation no matter what, there
isn't the need to use __must_check with it. It can very well
be optional.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC
-off-by: Glauber Costa glom...@parallels.com
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
The code itself seems fine.
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
, and will release the index for other caches.
This index mechanism was developed by Suleiman Souhlal.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Christoph Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki
Lameter c...@linux.com
CC: Pekka Enberg penb...@cs.helsinki.fi
CC: Michal Hocko mho...@suse.cz
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Johannes Weiner han...@cmpxchg.org
CC: Suleiman Souhlal sulei...@google.com
Seems reasonable.
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir
(2012/04/24 23:22), Frederic Weisbecker wrote:
On Mon, Apr 23, 2012 at 03:25:59PM -0700, David Rientjes wrote:
On Sun, 22 Apr 2012, Glauber Costa wrote:
+/*
+ * Return the kmem_cache we're supposed to use for a slab allocation.
+ * If we are in interrupt context or otherwise have an
destruction point and was already marked as dead.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Tejun Heo t...@kernel.org
CC: Li Zefan lize...@huawei.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
---
kernel
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
___
Devel mailing list
Devel@openvz.org
https://openvz.org/mailman/listinfo/devel
Zefan lize...@huawei.com
CC: Kamezawa Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: Vivek Goyal vgo...@redhat.com
---
kernel/cgroup.c |9 -
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index 932c318..976d332 100644
--- a/kernel
...@parallels.com
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
A small request below.
snip
+ * -activated needs to be written after the static_key update.
+ * This is what guarantees that the socket activation function
+ * is the last
(2012/04/20 7:49), Glauber Costa wrote:
We call the destroy function when a cgroup starts to be removed,
such as by a rmdir event.
However, because of our reference counters, some objects are still
inflight. Right now, we are decrementing the static_keys at destroy()
time, meaning that if
(2012/03/30 22:53), Glauber Costa wrote:
On 03/30/2012 11:58 AM, KAMEZAWA Hiroyuki wrote:
==
Now, we do consume 'reserved' usage, we can avoid css_get(), an heavy atomic
ops. You may need to move this code as
rcu_read_lock()
res_counter_charge()
if (failure
(2012/03/30 17:04), Glauber Costa wrote:
Hi,
Here is my take about how we can make res_counter updates faster.
Keep in mind this is a bit of a hack intended as a proof of concept.
The pros I see with this:
* free updates in non-constrained paths. non-constrained paths includes
(2012/03/30 17:04), Glauber Costa wrote:
This is the bulk of the proposal.
Updates to the res_counter are done to the percpu area, if we are
inside what we can call the safe zone.
The safe zone is whenever we are far enough from the limit to be
sure this update won't touch it. It is bigger
(2012/03/30 18:33), KAMEZAWA Hiroyuki wrote:
(2012/03/30 17:04), Glauber Costa wrote:
Hmm this part doesn't seem very good.
I don't think for_each_online_cpu() here will not be a way to the final win.
Under multiple hierarchy, you may need to call for_each_online_cpu() in each
level
code behavior because that's the standard =)
Time to fix it, then.
Signed-off-by: Glauber Costa glom...@parallels.com
Cc: Johannes Weiner han...@cmpxchg.org
Cc: Michal Hocko mho...@suse.cz
Cc: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir
(2012/03/14 21:29), Glauber Costa wrote:
- What happens when a new cgroup created ?
mem_cgroup_create() is called =)
Heh, jokes apart, I don't really follow here. What exactly do you mean?
There shouldn't be anything extremely out of the ordinary.
Sorry, too short words.
Assume a
On Sun, 11 Mar 2012 12:12:04 +0400
Glauber Costa glom...@parallels.com wrote:
On 03/10/2012 12:39 AM, Suleiman Souhlal wrote:
Enabled with CONFIG_CGROUP_MEM_RES_CTLR_KMEM.
Adds the following files:
- memory.kmem.independent_kmem_limit
- memory.kmem.usage_in_bytes
-
On Fri, 9 Mar 2012 12:39:06 -0800
Suleiman Souhlal ssouh...@freebsd.org wrote:
Signed-off-by: Suleiman Souhlal sulei...@google.com
---
mm/memcontrol.c | 31 ++-
1 files changed, 30 insertions(+), 1 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
On Tue, 13 Mar 2012 14:37:30 +0400
Glauber Costa glom...@parallels.com wrote:
After looking codes, I think we need to think
whether independent_kmem_limit is good or not
How about adding MEMCG_KMEM_ACCOUNT flag instead of this and use only
memcg-res/memcg-memsw rather than adding a
On Wed, 29 Feb 2012 11:09:50 -0800
Suleiman Souhlal sulei...@google.com wrote:
On Tue, Feb 28, 2012 at 10:00 PM, KAMEZAWA Hiroyuki
kamezawa.hir...@jp.fujitsu.com wrote:
On Mon, 27 Feb 2012 14:58:47 -0800
Suleiman Souhlal ssouh...@freebsd.org wrote:
This is used to indicate that we don't
On Wed, 29 Feb 2012 14:30:35 -0300
Glauber Costa glom...@parallels.com wrote:
On 02/22/2012 12:01 PM, Glauber Costa wrote:
On 02/22/2012 04:46 AM, KAMEZAWA Hiroyuki wrote:
On Tue, 21 Feb 2012 15:34:33 +0400
Glauber Costaglom...@parallels.com wrote:
Move some hardcoded definitions
On Wed, 29 Feb 2012 21:24:11 -0300
Glauber Costa glom...@parallels.com wrote:
On 02/29/2012 09:10 PM, KAMEZAWA Hiroyuki wrote:
On Wed, 29 Feb 2012 11:09:50 -0800
Suleiman Souhlalsulei...@google.com wrote:
On Tue, Feb 28, 2012 at 10:00 PM, KAMEZAWA Hiroyuki
kamezawa.hir
On Tue, 28 Feb 2012 15:36:27 -0800
Suleiman Souhlal sulei...@google.com wrote:
On Tue, Feb 28, 2012 at 5:34 AM, Glauber Costa glom...@parallels.com wrote:
On 02/27/2012 07:58 PM, Suleiman Souhlal wrote:
This config option dictates whether or not kernel memory in the
root cgroup should be
On Mon, 27 Feb 2012 14:58:47 -0800
Suleiman Souhlal ssouh...@freebsd.org wrote:
This is used to indicate that we don't want an allocation to be accounted
to the current cgroup.
Signed-off-by: Suleiman Souhlal sulei...@google.com
I don't like this.
Please add
___GFP_ACCOUNT account this
On Mon, 27 Feb 2012 14:58:46 -0800
Suleiman Souhlal ssouh...@freebsd.org wrote:
From: Hugh Dickins hu...@google.com
mem_cgroup_do_charge() was written before slab accounting, and expects
three cases: being called for 1 page, being called for a stock of 32 pages,
or being called for a
On Mon, 27 Feb 2012 14:58:45 -0800
Suleiman Souhlal ssouh...@freebsd.org wrote:
A later patch will also use this to move the accounting to the root
cgroup.
Signed-off-by: Suleiman Souhlal sulei...@google.com
---
mm/memcontrol.c | 30 +-
1 files changed, 29
...@redhat.com
CC: Michal Hocko mho...@suse.cz
CC: Hiroyouki Kamezawa kamezawa.hir...@jp.fujitsu.com
CC: Paul Turner p...@google.com
CC: Frederic Weisbecker fweis...@gmail.com
seems ok to me.
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
a nitpick..
---
mm/memcontrol.c | 10
On Tue, 21 Feb 2012 15:34:35 +0400
Glauber Costa glom...@parallels.com wrote:
This patch creates the infrastructure to allow us to register
per-memcg slab caches. As an example implementation, I am tracking
the dentry cache, but others will follow.
I am using an opt-in istead of opt-out
On Tue, 21 Feb 2012 15:34:36 +0400
Glauber Costa glom...@parallels.com wrote:
In the context of tracking kernel memory objects to a cgroup, the
following problem appears: we may need to destroy a cgroup, but
this does not guarantee that all objects inside the cache are dead.
This can't be
On Tue, 21 Feb 2012 15:34:37 +0400
Glauber Costa glom...@parallels.com wrote:
This patch adds the shrinker interface to memcg proposed kmem
controller. With this, softlimits starts being meaningful. I didn't
played to much with softlimits itself, since it is a bit in progress
for the general
On Mon, 12 Dec 2011 11:47:00 +0400
Glauber Costa glom...@parallels.com wrote:
Hi,
This series fixes all the few comments raised in the last round,
and seem to have acquired consensus from the memcg side.
Dave, do you think it is acceptable now from the networking PoV?
In case positive,
On Sun, 11 Dec 2011 15:50:56 +0100
Glauber Costa glom...@parallels.com wrote:
On 12/09/2011 03:55 PM, Glauber Costa wrote:
On 12/09/2011 12:03 PM, Peter Zijlstra wrote:
On Mon, 2011-12-05 at 07:32 -0200, Glauber Costa wrote:
Hi,
Specially Peter and Paul, but all the others:
As you
On Fri, 9 Dec 2011 10:43:00 -0200
Glauber Costa glom...@parallels.com wrote:
On 12/09/2011 12:05 AM, KAMEZAWA Hiroyuki wrote:
On Mon, 5 Dec 2011 19:34:57 -0200
Glauber Costaglom...@parallels.com wrote:
The goal of this work is to move the memory pressure tcp
controls to a cgroup
On Fri, 9 Dec 2011 12:37:23 -0200
Glauber Costa glom...@parallels.com wrote:
On 12/08/2011 11:21 PM, KAMEZAWA Hiroyuki wrote:
Hm, why you check val != parent-kmem_independent_accounting ?
if (parent parent-use_hierarchy)
return -EINVAL;
?
BTW, you didn't check
kamezawa.hir...@jp.fujitsu.com
CC: Eric W. Biederman ebied...@xmission.com
CC: Eric Dumazet eric.duma...@gmail.com
please get ack from network guys.
from me.
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
___
Devel mailing list
Devel
nothing
tcp-specific.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Kirill A. Shutemov kir...@shutemov.name
CC: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujtsu.com
CC: David S. Miller da...@davemloft.net
CC: Eric W. Biederman ebied...@xmission.com
CC: Eric Dumazet eric.duma...@gmail.com
-by: Glauber Costa glom...@parallels.com
CC: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujtisu.com
CC: Eric W. Biederman ebied...@xmission.com
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
___
Devel mailing list
Devel@openvz.org
https
in the
patches that follows in this patchset.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
CC: David S. Miller da...@davemloft.net
CC: Eric W. Biederman ebied...@xmission.com
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir
...@parallels.com
CC: David S. Miller da...@davemloft.net
CC: Hiroyouki Kamezawa kamezawa.hir...@jp.fujitsu.com
CC: Eric W. Biederman ebied...@xmission.com
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
___
Devel mailing list
Devel@openvz.org
https
-by: Glauber Costa glom...@parallels.com
Reviewed-by: Hiroyouki Kamezawa kamezawa.hir...@jp.fujitsu.com
CC: David S. Miller da...@davemloft.net
CC: Eric W. Biederman ebied...@xmission.com
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
. Biederman ebied...@xmission.com
Reviewed-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
___
Devel mailing list
Devel@openvz.org
https://openvz.org/mailman/listinfo/devel
nothing
tcp-specific.
Signed-off-by: Glauber Costa glom...@parallels.com
CC: Kirill A. Shutemov kir...@shutemov.name
CC: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujtsu.com
CC: David S. Miller da...@davemloft.net
CC: Eric W. Biederman ebied...@xmission.com
CC: Eric Dumazet eric.duma...@gmail.com
On Mon, 5 Dec 2011 07:09:51 -0200
Glauber Costa glom...@parallels.com wrote:
On 12/05/2011 12:06 AM, KAMEZAWA Hiroyuki wrote:
On Fri, 2 Dec 2011 16:04:08 -0200
Glauber Costaglom...@parallels.com wrote:
On 11/30/2011 12:11 AM, KAMEZAWA Hiroyuki wrote:
On Tue, 29 Nov 2011 21:56:51 -0200
On Mon, 5 Dec 2011 07:32:33 -0200
Glauber Costa glom...@parallels.com wrote:
Hi,
Specially Peter and Paul, but all the others:
As you can see in https://lkml.org/lkml/2011/12/4/178, and in my answer
to that, there is a question - one I've asked before but without that
much of an
On Fri, 2 Dec 2011 15:46:46 -0200
Glauber Costa glom...@parallels.com wrote:
static void proto_seq_printf(struct seq_file *seq, struct proto *proto)
{
+ struct mem_cgroup *memcg = mem_cgroup_from_task(current);
+
seq_printf(seq, %-9s %4u %6d %6ld %-3s %6u %-3s %-10s
On Fri, 2 Dec 2011 15:57:28 -0200
Glauber Costa glom...@parallels.com wrote:
On 11/29/2011 11:49 PM, KAMEZAWA Hiroyuki wrote:
-static struct mem_cgroup *mem_cgroup_from_cont(struct cgroup *cont)
+struct mem_cgroup *mem_cgroup_from_cont(struct cgroup *cont)
{
return container_of
1 - 100 of 728 matches
Mail list logo