From: "Olivier Crête" <olivier.crete@collabora.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: libva decoding performance regression with kernel 4.0-rc
Date: Fri, 10 Apr 2015 19:25:59 -0400 [thread overview]
Message-ID: <1428708359.3417.39.camel@collabora.com> (raw)
In-Reply-To: <20150410062331.GE20904@nuc-i3427.alporthouse.com>
Hello,
Thanks for the quick reply!
With my real use-cases:
1. 9x 720p60 mpeg2 videos
- 4.0-rc6: ~12 frames per second are on time
- 4.0-rc6 + reverts: a stable 45 frames per second are on time
- 044307a9: 40-45 frames per second are on time
- 0a24802a: 45-46 frames per second are on time
2. 1080i30 mpeg2 videos
- 4.0-rc6: 5 videos
- 044307a9: 10 videos
- 0a24802a: 10 videos
So you basically beat my baseline too, good job, thanks a lot! Any
chance you can sneak this into 4.0 ?
Olivier
On Fri, 2015-04-10 at 07:23 +0100, Chris Wilson wrote:
> On Thu, Apr 09, 2015 at 09:00:43PM -0400, Olivier Crête wrote:
> > Hello,
> >
> > Using an Atom E3845 board, we had a pretty bad performance regression
> > when upgrading to 4.0-rc6 from 3.19. With the help of git bisect, I
> > traced it back to commit 78a42377. Reverting this commit and subsequent
> > related commits (b9ffd80, 71745376, etc) fixes the performance
> > regression for me.
>
> Can you please test
>
> http://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=for-olivier-crete
>
> on your setup.
>
> First
> http://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=for-olivier-crete&id=044307a99b418258ac0d775460d73b20b80277c1
> to get a baseline with nightly as that contains some fine tuning to the
> batch allocations, which is pretty significant for libva on Atom (only
> double clflushing one or two pages every batch rather than 128) and then
> http://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=for-olivier-crete&id=0a24802a5b61403b887ce401ce3efd52f5fd1eac
> to see if the command parser tuning helps.
>
> Hope this helps,
> -Chris
>
--
Olivier Crête
olivier.crete@collabora.com
prev parent reply other threads:[~2015-04-10 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 1:00 libva decoding performance regression with kernel 4.0-rc Olivier Crête
2015-04-10 6:23 ` Chris Wilson
2015-04-10 23:25 ` Olivier Crête [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428708359.3417.39.camel@collabora.com \
--to=olivier.crete@collabora.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox