[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <484FAC37.90300@gmail.com>
Date: Wed, 11 Jun 2008 12:43:03 +0200 (MEST)
From: Andrea Righi <righi.andrea@...il.com>
To: Dave Hansen <dave@...ux.vnet.ibm.com>
Cc: balbir@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
kosaki.motohiro@...fujitsu.com, containers@...ts.osdl.org,
menage@...gle.com, xemul@...nvz.org
Subject: Re: [RFC PATCH 3/5] mgmcg VM overcommit interface
Dave Hansen wrote:
> On Tue, 2008-06-10 at 01:33 +0200, Andrea Righi wrote:
>> + cgroup_unlock();
>> +
>> + count = sprintf(page, "CommitLimit: %8lu kB\n"
>> + "Committed_AS: %8lu kB\n",
>> + K(allowed), K(committed));
>> + ret = simple_read_from_buffer(userbuf, nbytes, ppos, page, count);
>> +out:
>> + free_page((unsigned long)page);
>> + return ret;
>> +}
>
> I know you're trying to make this look like meminfo, but it does butcher
> the sysfs rules a bit. How about breaking it out into a couple of
> files?
>
> -- Dave
Sounds reasonable.
Anyway, I think this patchset should be simply dropped in favor of the
Balbir's memrlimit controller, as reported by Kamezawa.
The memrlimit controller permits to implement the overcommit policies in
userspace directly setting the cgroup VM limits (well.. I've not read the
memrlimit source yet, but from the documentation it seems so).
-Andrea
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists