On Tue, 2006-12-19 at 13:47 +0100, Thomas HellstrÃm wrote:Nope. These structures get allocated once per display memory buffer, and a display memory buffer may be as large as
Arjan van de Ven wrote:
Hmm,A short background:but if it's clearly the right thing.....
The current code uses vmalloc only. The potential use of kmalloc was introduced
to save memory and cpu-speed.
All agp drivers expect to see a single memory chunk, so I'm not sure we want to have an array of pages. That may require rewriting a lot of code.
How hard can it be? there are what.. 5 or 6 AGP drivers in the kernel?
but we would still waste a lot of memory compared to kmalloc,
surely it's at most 4Kb for the entire system?
(if agp allows the non-root user to pin a lot more than that in kernelThe drm memory manager sets aside and keeps track of a preset amount of memory that can be pinned in the kernel for video use, which is shared by all users running direct rendering clients. Currently this is a hard limit, but the idea is to unlock memory and make it swappable if resources become scarce. The memory we're discussing above is included in the bookkeeping.
memory there is a different problem of rlimits ;)