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
| ||
|
Date: Thu, 18 Sep 2008 13:50:23 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: Hirokazu Takahashi <taka@...inux.co.jp> Cc: akpm@...ux-foundation.org, balbir@...ux.vnet.ibm.com, dave@...ux.vnet.ibm.com, nickpiggin@...oo.com.au, hugh@...itas.com, menage@...gle.com, xemul@...nvz.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [RFC][PATCH] Remove cgroup member from struct page (v3) On Thu, 18 Sep 2008 13:26:13 +0900 (JST) Hirokazu Takahashi <taka@...inux.co.jp> wrote: > But I think each memory model type should have its own way of managing > its page_cgroup arrays as doing for its struct page arrays. > It would be better rather than the sparsemem approach he said. > My patch adds an interface. Then... FLATMEM support will be very easy. I'll ignore DISCONTIGMEM and SPARSEMEM (they will use my 'hash') SPARSEMEM_VMEMMAP support will took some amount of time. It will need per-arch patches. Thanks, -Kame -- 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/
Powered by blists - more mailing lists