Re: [Patch] Hashed map lookup.

2006-07-11 Thread Thomas Hellström
Thomas Hellström wrote: >Another option is to try to keep the current functionality, setting >(handle == physical address) for 32 bit mappings of device addresses, >and squeeze 64-bit device addresses and TTMs into the window starting >at 0x1000. I think this is the route of minimal impact

Re: [Patch] Hashed map lookup.

2006-07-11 Thread Thomas Hellström
Dave Airlie wrote: > >>> i've thought about this, we probably need to make handle hashing a >>> driver option, if a driver is currently safe then we can just set it >>> by default for that driver, however otherwise we should use a >>> setparam from the DDX to tell the driver that the DDX is at

Re: [Patch] Hashed map lookup.

2006-07-10 Thread Dave Airlie
> > Can we do this without upping the driver majors? we may have to add > setparam support... my problem is after this change, old 2D driver may > not work anymore with this DRM, so if I upgrade my kernel it will break > things that currently work... we managed to mostly avoid this with the > 64-bi

Re: [Patch] Hashed map lookup.

2006-07-10 Thread Dave Airlie
>> > I just did this and fixed the SiS and Unichrome 3D drivers, bumping their > drm device driver majors. The fixes tend to be very small. The intel drivers > should also be OK. Can we do this without upping the driver majors? we may have to add setparam support... my problem is after this chan

Re: [Patch] Hashed map lookup.

2006-07-10 Thread Thomas Hellström
Dave Airlie wrote: I'd like to bring in the hashed map lookup from the drm-ttm-branch to CVS. It changes the drmmap() map lookup from a linked list search to a hash lookup. This means that the user_token that identifies the map in user space becomes an arbitrary hash key in the range

Re: [Patch] Hashed map lookup.

2006-07-05 Thread Dave Airlie
> > I'd like to bring in the hashed map lookup from the drm-ttm-branch to CVS. It > changes the drmmap() map lookup from a linked list search to a hash lookup. > > This means that the user_token that identifies the map in user space becomes > an arbitrary hash key in the range 0x1000 to 0x900

[Patch] Hashed map lookup.

2006-07-05 Thread Thomas Hellström
Hi, All. I'd like to bring in the hashed map lookup from the drm-ttm-branch to CVS. It changes the drmmap() map lookup from a linked list search to a hash lookup. This means that the user_token that identifies the map in user space becomes an arbitrary hash key in the range 0x1000 to 0x9