[PATCH 1/3] drm: create unified vma offset manager

2012-12-19 Thread Dave Airlie
From: Dave Airlie So we have to offset manager implementations for dealing with VMA offsets. GEM had one using the hash table, TTM had one using an rbtree, I'd rather we just had one to rule them all, since ttm is using the rbtree variant to allow sub mappings, to keep ABI we need to use that on

[PATCH 1/3] drm: create unified vma offset manager

2012-12-19 Thread Daniel Vetter
On Wed, Dec 19, 2012 at 09:22:26AM +, Chris Wilson wrote: > On Wed, 19 Dec 2012 11:56:18 +1000, Dave Airlie wrote: > > From: Dave Airlie > > > > So we have to offset manager implementations for dealing with VMA offsets. > > GEM had one using the hash table, TTM had one using an rbtree, > >

[PATCH 1/3] drm: create unified vma offset manager

2012-12-19 Thread Chris Wilson
On Wed, 19 Dec 2012 11:56:18 +1000, Dave Airlie wrote: > From: Dave Airlie > > So we have to offset manager implementations for dealing with VMA offsets. > GEM had one using the hash table, TTM had one using an rbtree, > > I'd rather we just had one to rule them all, since ttm is using the rbtr

Re: [PATCH 1/3] drm: create unified vma offset manager

2012-12-19 Thread Daniel Vetter
On Wed, Dec 19, 2012 at 09:22:26AM +, Chris Wilson wrote: > On Wed, 19 Dec 2012 11:56:18 +1000, Dave Airlie wrote: > > From: Dave Airlie > > > > So we have to offset manager implementations for dealing with VMA offsets. > > GEM had one using the hash table, TTM had one using an rbtree, > >

Re: [PATCH 1/3] drm: create unified vma offset manager

2012-12-19 Thread Chris Wilson
On Wed, 19 Dec 2012 11:56:18 +1000, Dave Airlie wrote: > From: Dave Airlie > > So we have to offset manager implementations for dealing with VMA offsets. > GEM had one using the hash table, TTM had one using an rbtree, > > I'd rather we just had one to rule them all, since ttm is using the rbtr

[PATCH 1/3] drm: create unified vma offset manager

2012-12-18 Thread Dave Airlie
From: Dave Airlie So we have to offset manager implementations for dealing with VMA offsets. GEM had one using the hash table, TTM had one using an rbtree, I'd rather we just had one to rule them all, since ttm is using the rbtree variant to allow sub mappings, to keep ABI we need to use that on