Hi All,
I thought I would clarify what is in store for the next few linaro cycles from a libjpeg-turbo perspective.
11.08 1.1.2 libjpeg-turbo (featuring cleaned up patches) upstreaming and support of what could be a late august upstream 1.2 release
11.09 1.2 upstream based linaro release (presuming upstream releases) Upstreaming / rework of android delta
Beyond this point isn't fully vetted and merely represents possible action.
11.10 effort to optimize encode path 1.2.1 libjpeg-turbo release including encode optimizations
On Wed, Aug 10, 2011 at 3:45 PM, Tom Gall tom.gall@linaro.org wrote:
Hi All,
I thought I would clarify what is in store for the next few linaro cycles from a libjpeg-turbo perspective.
11.08 1.1.2 libjpeg-turbo (featuring cleaned up patches) upstreaming and support of what could be a late august upstream 1.2 release
Does this involve adding easy/automatic benchmarks so we can track a) improvements turbo gives over plain and b) improvements we do to turbo over time? If not, I would very much like to see that that's part early phases of the plan.
On Wed, Aug 10, 2011 at 9:05 AM, Alexander Sack asac@linaro.org wrote:
On Wed, Aug 10, 2011 at 3:45 PM, Tom Gall tom.gall@linaro.org wrote:
Hi All,
I thought I would clarify what is in store for the next few linaro cycles from a libjpeg-turbo perspective.
11.08 1.1.2 libjpeg-turbo (featuring cleaned up patches) upstreaming and support of what could be a late august upstream 1.2 release
Does this involve adding easy/automatic benchmarks so we can track a) improvements turbo gives over plain and b) improvements we do to turbo over time? If not, I would very much like to see that that's part early phases of the plan.
1.1.1 includes in cjpeg and djpeg (encode and decode respectively) timing code for measurement. Make test also includes timing code. It's less than perfect but it's there.
Upstream 1.2's make test is improved and more fleshed out.
Could it be better? When can code never be improved or have more and better test? ;-)
On Wed, Aug 10, 2011 at 4:18 PM, Tom Gall tom.gall@linaro.org wrote:
On Wed, Aug 10, 2011 at 9:05 AM, Alexander Sack asac@linaro.org wrote:
On Wed, Aug 10, 2011 at 3:45 PM, Tom Gall tom.gall@linaro.org wrote:
Hi All,
I thought I would clarify what is in store for the next few linaro cycles from a libjpeg-turbo perspective.
11.08 1.1.2 libjpeg-turbo (featuring cleaned up patches) upstreaming and support of what could be a late august upstream 1.2 release
Does this involve adding easy/automatic benchmarks so we can track a) improvements turbo gives over plain and b) improvements we do to turbo over time? If not, I would very much like to see that that's part early phases of the plan.
1.1.1 includes in cjpeg and djpeg (encode and decode respectively) timing code for measurement. Make test also includes timing code. It's less than perfect but it's there.
Upstream 1.2's make test is improved and more fleshed out.
Could it be better? When can code never be improved or have more and better test? ;-)
Cool. Is hooking this up into lava-test framework for daily runs in the lab part of the current plan? If not, could you try to include that somehow?
On Wed, Aug 10, 2011 at 09:18:04AM -0500, Tom Gall wrote:
On Wed, Aug 10, 2011 at 9:05 AM, Alexander Sack asac@linaro.org wrote:
Does this involve adding easy/automatic benchmarks so we can track a) improvements turbo gives over plain and b) improvements we do to turbo over time? If not, I would very much like to see that that's part early phases of the plan.
1.1.1 includes in cjpeg and djpeg (encode and decode respectively) timing code for measurement. Make test also includes timing code. It's less than perfect but it's there.
Do we have a vanilla libjpeg run to compare against (and/or can we ensure we keep that handy for easy comparison)?
On Wed, Aug 10, 2011 at 10:05 AM, Christian Robottom Reis kiko@linaro.org wrote:
On Wed, Aug 10, 2011 at 09:18:04AM -0500, Tom Gall wrote:
On Wed, Aug 10, 2011 at 9:05 AM, Alexander Sack asac@linaro.org wrote:
Does this involve adding easy/automatic benchmarks so we can track a) improvements turbo gives over plain and b) improvements we do to turbo over time? If not, I would very much like to see that that's part early phases of the plan.
1.1.1 includes in cjpeg and djpeg (encode and decode respectively) timing code for measurement. Make test also includes timing code. It's less than perfect but it's there.
Do we have a vanilla libjpeg run to compare against (and/or can we ensure we keep that handy for easy comparison)?
Yes and there is of course the ubuntu libjpeg62 version.
-
Alexander Sack -
Christian Robottom Reis -
Tom Gall