linux-kernel - Re: [PATCH -mmotm] memcg: implement memory thresholds document fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 Jan 2010 10:34:17 +0900
From:	Daisuke Nishimura <nishimura@....nes.nec.co.jp>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	akpm@...ux-foundation.org, LKML <linux-kernel@...r.kernel.org>,
	"Kirill A. Shutemov" <kirill@...temov.name>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	Daisuke Nishimura <nishimura@....nes.nec.co.jp>
Subject: Re: [PATCH -mmotm] memcg: implement memory thresholds document
 fixes

On Thu, 7 Jan 2010 10:18:05 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:
> On Thu, 7 Jan 2010 09:57:14 +0900
> Daisuke Nishimura <nishimura@....nes.nec.co.jp> wrote:
> 
> > Each memcg-implement-memory-thresholds.patch and
> > memcg-add-interface-to-move-charge-at-task-migration.patch try to add a new
> > section to Documentation/cgroup/memory.txt, so the document has been a bit
> > mangled when these patches are merged at the same time.
> > 
> > This patch fixes it.
> > 
> 
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
> 
> BTW, I'll prepare total update for memcg (especially around percpu counter).
> Do you have something may conflict in plan ?
> 
Not for now.
Of course, I have a plan that I will add a file/shmem page support to move-charge feature,
but I think we should stabilize and clean up current memcg in mmotm first.
(My biggest concern now is the influence of transparent hugepage to vm and memcg.)


Thanks,
Daisuke Nishimura.
--
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/