Hello,
> > But I think each memory model type should have its own way of managing
Yes, that is true, it is really easy.
> I'll ignore DISCONTIGMEM and SPARSEMEM (they will use my 'hash')
What part of this do you think is the problem to implement it in the
straight way for this model?
I think it won't be difficult to implement it since each pgdat can have
its page_cgroup array, which can care about holes in the node as well as
doing it for its struct page array.
> SPARSEMEM_VMEMMAP support will took some amount of time. It will need
Yes, each of ia64, powerpc and x86_64 use this memory model.
We should also care about the regular SPARSEMEM case as you mentioned.
> Thanks,
--
| Kamalesh Babulal | [BUG] Linux 2.6.25-rc2 - Kernel Ooops while running dbench |
| Vu Pham | Re: [Scst-devel] Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Gabriel C | Re: Linux 2.6.21-rc2 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Jeff Garzik | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
