On Mon, 29 Mar 2010 20:37:13 +0200 Andrea Arcangeli <aarcange@xxxxxxxxxx> wrote: > Hello Andrew, > > This is again against 2.6.34-rc1-mm1+ as before (I didn't find any newer -mm). > > This removes PG_buddy and allows the PAE 32bit build with CONFIG_X86_PAT=y && > CONFIG_X86_PAE=y && CONFIG_SPARSEMEM =y and fixes two bits in memcg_compound. > > Removing an unconditional unnecessary PG_ bitflag is overall a gain anyway > (the added one is conditional to CONFIG_TRANSPARENT_HUGEPAGE which could be > turned off on 32bit archs depending on which feature is more or less important > to the user configuring the kernel). > > http://www.kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.34-rc2-mm1/transparent_hugepage-16/ > http://www.kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.34-rc2-mm1/transparent_hugepage-16.gz > Hmm, recently, I noticed that x86-64 has hugepage_size == pmd_size but we can't assume that in generic. I know your code depends on x86-64 by CONFIG. Can this implementation be enhanced for various hugepage in generic archs ? I doubt based-on-pmd approach will get sucess in generic archs.. I'm sorry if you answered someone already. Thanks, -Kame -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>