From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: linux-arm-kernel@lists.infradead.org
Subject: [NEW]: Introducing shrink_all_memory from user space
Date: Wed, 18 Apr 2012 21:10:32 +0100 [thread overview]
Message-ID: <20120418211032.47b243da@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAFLxGvz5tmEi-39CZbJN+0zNd3ZpHXzZcNSFUpUWS_aMDJ4t6Q@mail.gmail.com>
On Sun, 15 Apr 2012 14:10:00 +0200
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:
> On Sun, Apr 15, 2012 at 1:47 PM, PINTU KUMAR <pintu_agarwal@yahoo.com> wrote:
> > Moreover, this is mainly meant for mobile phones where there is only *one* user.
>
> I see. Jet another awful hack.
> Mobile phones are nothing special. They are computers
Correct - so if it is showing up useful situations then they are also
useful beyond mobile phone.
> Every program which is allowed to use this interface will (ab)use it.
If you expose it to userspace then you would want it very tightly
controlled and very much special case. Within the kernel using it
internally within things like CMA allocators seems to make more sense.
I think you overestimate the abuse. It's an interface which pushes clean
pages that can be cheaply recovered out of memory. It doesn't guarantee
the caller reaps the benefit of that, and the vm will continue to try and
share out any new resource fairly.
Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: PINTU KUMAR <pintu_agarwal@yahoo.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"pintu.k@samsung.com" <pintu.k@samsung.com>
Subject: Re: [NEW]: Introducing shrink_all_memory from user space
Date: Wed, 18 Apr 2012 21:10:32 +0100 [thread overview]
Message-ID: <20120418211032.47b243da@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAFLxGvz5tmEi-39CZbJN+0zNd3ZpHXzZcNSFUpUWS_aMDJ4t6Q@mail.gmail.com>
On Sun, 15 Apr 2012 14:10:00 +0200
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:
> On Sun, Apr 15, 2012 at 1:47 PM, PINTU KUMAR <pintu_agarwal@yahoo.com> wrote:
> > Moreover, this is mainly meant for mobile phones where there is only *one* user.
>
> I see. Jet another awful hack.
> Mobile phones are nothing special. They are computers
Correct - so if it is showing up useful situations then they are also
useful beyond mobile phone.
> Every program which is allowed to use this interface will (ab)use it.
If you expose it to userspace then you would want it very tightly
controlled and very much special case. Within the kernel using it
internally within things like CMA allocators seems to make more sense.
I think you overestimate the abuse. It's an interface which pushes clean
pages that can be cheaply recovered out of memory. It doesn't guarantee
the caller reaps the benefit of that, and the vm will continue to try and
share out any new resource fairly.
Alan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: PINTU KUMAR <pintu_agarwal@yahoo.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"pintu.k@samsung.com" <pintu.k@samsung.com>
Subject: Re: [NEW]: Introducing shrink_all_memory from user space
Date: Wed, 18 Apr 2012 21:10:32 +0100 [thread overview]
Message-ID: <20120418211032.47b243da@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAFLxGvz5tmEi-39CZbJN+0zNd3ZpHXzZcNSFUpUWS_aMDJ4t6Q@mail.gmail.com>
On Sun, 15 Apr 2012 14:10:00 +0200
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:
> On Sun, Apr 15, 2012 at 1:47 PM, PINTU KUMAR <pintu_agarwal@yahoo.com> wrote:
> > Moreover, this is mainly meant for mobile phones where there is only *one* user.
>
> I see. Jet another awful hack.
> Mobile phones are nothing special. They are computers
Correct - so if it is showing up useful situations then they are also
useful beyond mobile phone.
> Every program which is allowed to use this interface will (ab)use it.
If you expose it to userspace then you would want it very tightly
controlled and very much special case. Within the kernel using it
internally within things like CMA allocators seems to make more sense.
I think you overestimate the abuse. It's an interface which pushes clean
pages that can be cheaply recovered out of memory. It doesn't guarantee
the caller reaps the benefit of that, and the vm will continue to try and
share out any new resource fairly.
Alan
next prev parent reply other threads:[~2012-04-18 20:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 9:47 [NEW]: Introducing shrink_all_memory from user space PINTU KUMAR
2012-04-15 9:47 ` PINTU KUMAR
2012-04-15 9:47 ` PINTU KUMAR
2012-04-15 10:00 ` santosh
2012-04-15 10:00 ` santosh
2012-04-15 10:00 ` santosh
2012-04-15 10:38 ` richard -rw- weinberger
2012-04-15 10:38 ` richard -rw- weinberger
2012-04-15 10:38 ` richard -rw- weinberger
2012-04-15 11:47 ` PINTU KUMAR
2012-04-15 11:47 ` PINTU KUMAR
2012-04-15 11:47 ` PINTU KUMAR
2012-04-15 12:10 ` richard -rw- weinberger
2012-04-15 12:10 ` richard -rw- weinberger
2012-04-15 12:10 ` richard -rw- weinberger
2012-04-16 9:16 ` PINTU KUMAR
2012-04-16 9:16 ` PINTU KUMAR
2012-04-16 9:16 ` PINTU KUMAR
2012-04-18 20:10 ` Alan Cox [this message]
2012-04-18 20:10 ` Alan Cox
2012-04-18 20:10 ` Alan Cox
2012-04-19 13:42 ` PINTU KUMAR
2012-04-19 13:42 ` PINTU KUMAR
2012-04-19 13:42 ` PINTU KUMAR
2013-01-13 15:32 ` Introducing Aggressive Low Memory Booster [1] PINTU KUMAR
2013-01-14 11:00 ` Bartlomiej Zolnierkiewicz
2013-01-14 11:00 ` Bartlomiej Zolnierkiewicz
2013-01-14 11:00 ` Bartlomiej Zolnierkiewicz
2013-01-20 16:03 ` PINTU KUMAR
2013-01-20 16:03 ` PINTU KUMAR
2013-01-20 16:03 ` PINTU KUMAR
2012-04-16 18:50 ` [NEW]: Introducing shrink_all_memory from user space Ying Han
2012-04-16 18:50 ` Ying Han
2012-04-16 18:50 ` Ying Han
2012-04-17 18:24 ` KOSAKI Motohiro
2012-04-17 18:24 ` KOSAKI Motohiro
2012-04-17 18:24 ` KOSAKI Motohiro
2012-04-18 20:07 ` Alan Cox
2012-04-18 20:07 ` Alan Cox
2012-04-18 20:07 ` Alan Cox
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=20120418211032.47b243da@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-arm-kernel@lists.infradead.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.