On 10/10/2014 11:35, Steven Newbury wrote:
On Thu, 2014-06-26 at 18:23 +0100, john.c.harri...@intel.com wrote:
From: John Harrison harri...@intel.com>
Implemented a batch buffer submission scheduler for the i915 DRM
driver.
Hi John,
I was just wondering what's happening with this patch series
On Thu, 2014-06-26 at 18:23 +0100, john.c.harri...@intel.com wrote:
> From: John Harrison harri...@intel.com>
>
> Implemented a batch buffer submission scheduler for the i915 DRM
> driver.
Hi John,
I was just wondering what's happening with this patch series? Are you
still working on it? Doe
On Fri, Jun 27, 2014 at 06:44:04AM +1000, Dave Airlie wrote:
> >
> > Implemented a batch buffer submission scheduler for the i915 DRM driver.
> >
>
> While this seems very interesting, you might want to address in the commit msg
> or the cover email
>
> a) why this is needed,
> b) any improvement
>
> Implemented a batch buffer submission scheduler for the i915 DRM driver.
>
While this seems very interesting, you might want to address in the commit msg
or the cover email
a) why this is needed,
b) any improvements in speed, power consumption or throughput it generates,
i.e. benchmarks.
als
From: John Harrison
Implemented a batch buffer submission scheduler for the i915 DRM driver.
The general theory of operation is that when batch buffers are submitted to the
driver, the execbuffer() code assigns a unique seqno value and then packages up
all the information required to execute the
