Hi
On Wed, Jan 21, 2009 at 8:20 AM, KOSAKI Motohiro
kosaki.motoh...@jp.fujitsu.com wrote:
Care to work on your mem_notify patch again and bring it up to date?
That would be a good place to start working from, right?
Unfortunately No ;)
I should rewrite memory notification patchset from
On Thu, 2 Apr 2009, Trilok Soni wrote:
Any updates on top of mem_notify v6 patches? Is there any WIP for
mem_notify with memcg infrastructure as you have pointed out above?
The /dev/mem_notify patches seem to have been abandoned, but there's still
an interest in a per-cgroup oom notifier.
Hi
[Greg KH g...@kroah.com]
but I don't think driver/staging is good place for non driver code.
The problem is, any patch must be reviewed by stakeholder, not maintenar
only.
then, the patch should post lkml and subsystem mailing list at first.
I like reviewed code than
Hi!
2009/1/30 Pavel Machek pa...@suse.cz:
Hi!
I never expected it to be merged. I wrote it to allow us to ship a product.
The top problem is, this file stay on non proper place.
then, MM folks don't review at all.
I think this patch need to receive MM folks review.
This patch solves
* Paul Mundt let...@linux-sh.org [090116 01:05]:
On Thu, Jan 15, 2009 at 03:44:04PM -0800, Greg KH wrote:
On Thu, Jan 15, 2009 at 07:02:48PM +0530, Trilok Soni wrote:
And there is one more lowmem driver developed by Nokia for Nokia 8xx
tablets it seems. CCed Tony Lindgren, Juha and
Hi!
I never expected it to be merged. I wrote it to allow us to ship a product.
The top problem is, this file stay on non proper place.
then, MM folks don't review at all.
I think this patch need to receive MM folks review.
This patch solves two problems for us:
1. It gives us more
On Thu, Jan 29, 2009 at 02:29:05PM +0900, KOSAKI Motohiro wrote:
I never expected it to be merged. I wrote it to allow us to ship a
product.
Then, please write DON'T MERGE ME on the top of patch description.
we can adjust our viewpoints.
The code will live in
[Greg KH g...@kroah.com]
but I don't think driver/staging is good place for non driver code.
The problem is, any patch must be reviewed by stakeholder, not maintenar
only.
then, the patch should post lkml and subsystem mailing list at first.
I like reviewed code than unreviewed code.
On Wed, Jan 28, 2009 at 5:48 PM, KOSAKI Motohiro
kosaki.motoh...@jp.fujitsu.com wrote:
To indicate that it is more expensive to restart a killed process than
a regular cache page.
I think you already know this answer isn't actual answer.
anybody know 1 mean expensive. a reviewer want to know
On Wed, 28 Jan 2009 18:51:07 -0800
Arve Hjønnevåg a...@android.com wrote:
static uint32_t lowmem_debug_level = 2;
static int lowmem_adj[6] = {
why do you choice [6]?
We use six levels.
if you don't consider other user and other usage case,
this file can't merge forever.
I
On Thu, Jan 29, 2009 at 12:45:55PM +0900, KAMEZAWA Hiroyuki wrote:
On Wed, 28 Jan 2009 18:51:07 -0800
Arve Hjønnevåg a...@android.com wrote:
static uint32_t lowmem_debug_level = 2;
static int lowmem_adj[6] = {
why do you choice [6]?
We use six levels.
if you don't
I never expected it to be merged. I wrote it to allow us to ship a
product.
Then, please write DON'T MERGE ME on the top of patch description.
we can adjust our viewpoints.
The code will live in the drivers/staging/ directory for now and not get
merged into the main portion of
On Thu, Jan 29, 2009 at 01:43:51PM +0900, KOSAKI Motohiro wrote:
I never expected it to be merged. I wrote it to allow us to ship a
product.
Then, please write DON'T MERGE ME on the top of patch description.
we can adjust our viewpoints.
The code will live in the
I never expected it to be merged. I wrote it to allow us to ship a
product.
Then, please write DON'T MERGE ME on the top of patch description.
we can adjust our viewpoints.
The code will live in the drivers/staging/ directory for now and not get
merged into the
On Fri, Jan 16, 2009 at 08:16:51PM +0900, KOSAKI Motohiro wrote:
As far as I know, embedded guys strong want to lowmem notification mecanism.
I think the big server guys also want the same thing :)
Yeah! I know, because my company is definitry big server vendor :)
At least, I and my
On Wed, Jan 21, 2009 at 11:50:48AM +0900, KOSAKI Motohiro wrote:
I should rewrite memory notification patchset from scratch.
the new version will construct on memcg infrastrcture.
Why?
last year, I received many feedback from lkml folks and my article reader.
(I monthly write kernel patch
On Thu, Jan 15, 2009 at 03:44:04PM -0800, Greg KH wrote:
On Thu, Jan 15, 2009 at 07:02:48PM +0530, Trilok Soni wrote:
And there is one more lowmem driver developed by Nokia for Nokia 8xx
tablets it seems. CCed Tony Lindgren, Juha and Viktor.
And there is one more lowmem driver developed by Nokia for Nokia 8xx
tablets it seems. CCed Tony Lindgren, Juha and Viktor.
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=blob;f=security/lowmem.c;h=ae78a530af39703e335ad769f1e6f097f63ec6dd;hb=HEAD
quick review.
325
also quick review to lowmemorykiller.c
#include linux/module.h
#include linux/kernel.h
#include linux/mm.h
#include linux/oom.h
#include linux/sched.h
static int lowmem_shrink(int nr_to_scan, gfp_t gfp_mask);
static struct shrinker lowmem_shrinker = {
.shrink = lowmem_shrink,
On Fri, Jan 16, 2009 at 08:16:51PM +0900, KOSAKI Motohiro wrote:
As far as I know, embedded guys strong want to lowmem notification mecanism.
I think the big server guys also want the same thing :)
At least, I and my mem_notify receive multiple contact from embedded
and JavaVM developer.
Hi Greg,
On Thu, Jan 15, 2009 at 5:42 AM, Greg KH g...@kroah.com wrote:
On Wed, Jan 14, 2009 at 03:32:38PM -0800, Arve Hjønnevåg wrote:
On Wed, Jan 14, 2009 at 3:17 PM, Greg KH g...@kroah.com wrote:
We actually use 6 different thresholds for killing processes. I don't
know what all the
On Thu, Jan 15, 2009 at 07:02:48PM +0530, Trilok Soni wrote:
Hi Greg,
On Thu, Jan 15, 2009 at 5:42 AM, Greg KH g...@kroah.com wrote:
On Wed, Jan 14, 2009 at 03:32:38PM -0800, Arve Hjønnevåg wrote:
On Wed, Jan 14, 2009 at 3:17 PM, Greg KH g...@kroah.com wrote:
We actually use 6 different
22 matches
Mail list logo
