Re: [PATCH] x86_64: Make NR_IRQS configurable in Kconfig

From: Andi Kleen
Date: Mon Aug 07 2006 - 22:15:47 EST

> And it's a pretty nasty one because it can get people into the situation
> where the kernel worked fine for those who released it, but users who
> happen to load more modules (or the right combination of them) will
> experience per-cpu memory exhaustion.

Yes, and a high value will waste a lot of memory for normal users.

> So shouldn't we being scaling the per-cpu memory as well?

If we move it into vmalloc space it would be easy to extend at runtime - just the
virtual address space would need to be prereserved, but then more pages
could be mapped. Maybe we should just do that instead of continuing to kludge around?

Drawback would be some more TLB misses.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at