All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"riel@redhat.com" <riel@redhat.com>
Subject: Re: [PATCH][for -mm] fix accounting in vmscan.c for memory controller
Date: Tue, 11 Dec 2007 11:06:12 +0530	[thread overview]
Message-ID: <475E21CC.7060408@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071211142911.4b8091d2.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> On Tue, 11 Dec 2007 10:44:36 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> 
>> Looks good to me.
>>
>> Acked-by: Balbir Singh <balbir@linux.vnet.ibm.com>
>>
>> TODO:
>>
>> 1. Should we have vm_events for the memory controller as well?
>>    May be in the longer term
>>
> 
> ALLOC_STALL is recoreded as failcnt, I think.
> I think DIRECT can be accoutned easily.

Thanks for clarifying

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"riel@redhat.com" <riel@redhat.com>
Subject: Re: [PATCH][for -mm] fix accounting in vmscan.c for memory controller
Date: Tue, 11 Dec 2007 11:06:12 +0530	[thread overview]
Message-ID: <475E21CC.7060408@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071211142911.4b8091d2.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> On Tue, 11 Dec 2007 10:44:36 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> 
>> Looks good to me.
>>
>> Acked-by: Balbir Singh <balbir@linux.vnet.ibm.com>
>>
>> TODO:
>>
>> 1. Should we have vm_events for the memory controller as well?
>>    May be in the longer term
>>
> 
> ALLOC_STALL is recoreded as failcnt, I think.
> I think DIRECT can be accoutned easily.

Thanks for clarifying

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-12-11  5:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11  2:26 [PATCH][for -mm] fix accounting in vmscan.c for memory controller KAMEZAWA Hiroyuki
2007-12-11  2:26 ` KAMEZAWA Hiroyuki
2007-12-11  5:14 ` Balbir Singh
2007-12-11  5:14   ` Balbir Singh
2007-12-11  5:29   ` KAMEZAWA Hiroyuki
2007-12-11  5:29     ` KAMEZAWA Hiroyuki
2007-12-11  5:36     ` Balbir Singh [this message]
2007-12-11  5:36       ` Balbir Singh
2007-12-11 11:24 ` KAMEZAWA Hiroyuki
2007-12-11 11:24   ` KAMEZAWA Hiroyuki

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=475E21CC.7060408@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    --cc=yamamoto@valinux.co.jp \
    /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.