lkml.org 
[lkml]   [2004]   [Aug]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: DRM code reorganization

>> ian: what about splitting the current memory management code into a
>> module that can be swapped for your new version?
>
>
> AFAIK, the only drivers that have any sort of in-kernel memory manager
> are the radeon (only used by the R200 driver) and i830. That memory
> manager only exists to support an NV_vertex_array_range-like extension
> that some Tungsten customers needed. I don't think there would be any
> benefit to making that swappable.
>
> Once the new memory manager is in, 80% (or more) of the code will be in
> user-mode anyway. The code that will be in the kernel should be generic
> enough to be completely sharable (i.e., in a generic DRM library).

Yes, the future is Ian's manager. The existing ones are built to be discarded
when something better comes along.

Keith

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:04    [W:0.091 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site