Re: [Intel-gfx] [PATCH 06/13] drm/i915: Remove use of gtt_mappable_entries

2013-01-17 Thread Daniel Vetter
On Thu, Jan 17, 2013 at 12:45:17PM -0800, Ben Widawsky wrote: > Mappable_end, ie. size is almost always what you want as opposed to the > number of entries. Since we already have that information, we can scrap > the number of entries and only calculate it when needed. > > If gtt_start is !0, this

[Intel-gfx] [PATCH 06/13] drm/i915: Remove use of gtt_mappable_entries

2013-01-17 Thread Ben Widawsky
Mappable_end, ie. size is almost always what you want as opposed to the number of entries. Since we already have that information, we can scrap the number of entries and only calculate it when needed. If gtt_start is !0, this will have slightly different behavior. This difference can only occur in

[Intel-gfx] [PATCH 06/13] drm/i915: Remove use of gtt_mappable_entries

2013-01-15 Thread Ben Widawsky
Mappable_end, ie. size is almost always what you want as opposed to the number of entries. Since we already have that information, we can scrap the number of entries and only calculate it when needed. If gtt_start is !0, this will have slightly different behavior. This difference can only occur in