* Christoph Lameter <clameter@sgi.com> wrote:yes, as i said in this thread already earlier today, the sparse chunking goes from 64MB to 128MB. (and hence, by virtue of !PAE having a 4GB physical address space, the # of sparse sections goes from 64 to 32 - you can see the full sparse sections printout in my latest crashlog in my previous mail, including the NR_MEM_SECTIONS printout.) Pretty please, could you pay more than cursory attention to this bug i already spent two full days on and which is blocking the v2.6.25 release? Your commits are all over the place in this code, and you are one of the maintainers as well. We've got 5000 lines of flux in mm/* in v2.6.25. I'm just guessing my way around, but right now my impression is that the current early memory setup code is unrobust, over-complex, occasionally butt-ugly to read code in high need of cleanups, simplifications and debug facilities, visibly plagued by hit-and-run changes with frequent typos and everything else you normally dont want to see in the core kernel. (Did i get your attention now? ;-) Ingo --
| Stephane Jourdois | Re: 2.6.21-rc4-mm1 [PATCH] init/missing_syscalls.h fix |
| David Brown | Re: Linux 2.6.21-rc2 |
| Andi Kleen | [PATCH] [1/12] x86: Work around mmio config space quirk on AMD Fam10h |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| David Miller | Re: [GIT]: Networking |
| David Woodhouse | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
git: | |
