tree 6fac03f7bfcc0935a793f384ab6ebd5f4d085e02
parent b1f559ecdc6026ef783ccadc62a61e7da906fcb4
author Chris Wilson <chris@chris-wilson.co.uk> 1294866693 +0000
committer Dave Airlie <airlied@redhat.com> 1298423739 +1000

drm: Trim the GEM mmap offset hashtab

Using an order 19 drm_ht for the mmap offsets is a little obscene. That
means that will a fully populated GTT with every single object mmaped at
least once in its lifetime, there will be exactly one object in each
bucket.

Typically systems only have at most a few thousand objects, though you
may see a KDE desktop hit 50000. And most of those should never be
mapped... On my systems, just using an order 10 ht would still have an
average occupancy less than 1, so apply a small safety factor and
use an order 12 ht, like the other mmap offset ht.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Dave Airlie <airlied@redhat.com>