On Thu, Feb 21, 2013 at 10:55:52PM -0800, Anton Vorontsov wrote:
> On Fri, Feb 22, 2013 at 08:56:08AM +0900, Minchan Kim wrote:
> > [...] The my point is that you have a plan to support? Why I have a
> > question is that you said your goal is to replace lowmemory killer
>
> In short: yes, of
On Fri, Feb 22, 2013 at 08:56:08AM +0900, Minchan Kim wrote:
> [...] The my point is that you have a plan to support? Why I have a
> question is that you said your goal is to replace lowmemory killer
In short: yes, of course, if the non-memcg interface will be in demand.
> but android don't have
Hi Anton,
On Thu, Feb 21, 2013 at 03:04:26PM -0800, Anton Vorontsov wrote:
> On Tue, Feb 19, 2013 at 04:21:28PM -0800, Tejun Heo wrote:
> > On Tue, Feb 19, 2013 at 4:17 PM, Minchan Kim wrote:
> > > Should we really enable memcg for just pressure notificaion in embedded
> > > side?
> > > I
On Tue, Feb 19, 2013 at 04:21:28PM -0800, Tejun Heo wrote:
> On Tue, Feb 19, 2013 at 4:17 PM, Minchan Kim wrote:
> > Should we really enable memcg for just pressure notificaion in embedded
> > side?
> > I didn't check the size(cgroup + memcg) and performance penalty but I don't
> > want
> > to
On Tue, Feb 19, 2013 at 04:21:28PM -0800, Tejun Heo wrote:
On Tue, Feb 19, 2013 at 4:17 PM, Minchan Kim minc...@kernel.org wrote:
Should we really enable memcg for just pressure notificaion in embedded
side?
I didn't check the size(cgroup + memcg) and performance penalty but I don't
Hi Anton,
On Thu, Feb 21, 2013 at 03:04:26PM -0800, Anton Vorontsov wrote:
On Tue, Feb 19, 2013 at 04:21:28PM -0800, Tejun Heo wrote:
On Tue, Feb 19, 2013 at 4:17 PM, Minchan Kim minc...@kernel.org wrote:
Should we really enable memcg for just pressure notificaion in embedded
side?
I
On Fri, Feb 22, 2013 at 08:56:08AM +0900, Minchan Kim wrote:
[...] The my point is that you have a plan to support? Why I have a
question is that you said your goal is to replace lowmemory killer
In short: yes, of course, if the non-memcg interface will be in demand.
but android don't have
On Thu, Feb 21, 2013 at 10:55:52PM -0800, Anton Vorontsov wrote:
On Fri, Feb 22, 2013 at 08:56:08AM +0900, Minchan Kim wrote:
[...] The my point is that you have a plan to support? Why I have a
question is that you said your goal is to replace lowmemory killer
In short: yes, of course, if
Hello,
On Tue, Feb 19, 2013 at 4:17 PM, Minchan Kim wrote:
> Should we really enable memcg for just pressure notificaion in embedded side?
> I didn't check the size(cgroup + memcg) and performance penalty but I don't
> want
> to add unnecessary overhead if it is possible.
> Do you have a plan
Hi Anton,
On Mon, Feb 18, 2013 at 08:40:12PM -0800, Anton Vorontsov wrote:
> With this patch userland applications that want to maintain the
> interactivity/memory allocation cost can use the pressure level
> notifications. The levels are defined like this:
>
> The "low" level means that the
Hi Anton,
On Mon, Feb 18, 2013 at 08:40:12PM -0800, Anton Vorontsov wrote:
With this patch userland applications that want to maintain the
interactivity/memory allocation cost can use the pressure level
notifications. The levels are defined like this:
The low level means that the system is
Hello,
On Tue, Feb 19, 2013 at 4:17 PM, Minchan Kim minc...@kernel.org wrote:
Should we really enable memcg for just pressure notificaion in embedded side?
I didn't check the size(cgroup + memcg) and performance penalty but I don't
want
to add unnecessary overhead if it is possible.
Do you
With this patch userland applications that want to maintain the
interactivity/memory allocation cost can use the pressure level
notifications. The levels are defined like this:
The "low" level means that the system is reclaiming memory for new
allocations. Monitoring this reclaiming activity
With this patch userland applications that want to maintain the
interactivity/memory allocation cost can use the pressure level
notifications. The levels are defined like this:
The low level means that the system is reclaiming memory for new
allocations. Monitoring this reclaiming activity might
14 matches
Mail list logo