From: Dave Gordon <david.s.gordon@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 3/3] Introduce & use new lightweight SGL iterators
Date: Fri, 20 May 2016 01:13:31 +0100 [thread overview]
Message-ID: <573E56AB.9040208@intel.com> (raw)
In-Reply-To: <20160519172752.GE3590@nuc-i3427.alporthouse.com>
On 19/05/2016 18:27, Chris Wilson wrote:
> On Tue, May 17, 2016 at 01:05:48PM +0100, Dave Gordon wrote:
>> On 17/05/16 11:34, Tvrtko Ursulin wrote:
>>> On 16/05/16 16:19, Dave Gordon wrote:
>>>> The existing for_each_sg_page() iterator is somewhat heavyweight, and is
>>>> limiting i915 driver performance in a few benchmarks. So here we
>>>> introduce somewhat lighter weight iterators, primarily for use with GEM
>>>> objects or other case where we need only deal with whole aligned pages.
>>> Interesting idea, if for nothing then for eliminating the dreaded
>>> st->nents of for_each_sg_page. :)
>>>
>>> Which benchmarks it improves and how much do you know?
>> I know nothing :)
>>
>> But last time I posted some easy-to-use iterators, Chris Wilson said
>> they didn't address his complaint, which was that the existing ones
>> were too slow.
> These aren't very good either... Compared to the sg iters I have:
>
> gem:exec:fault:1MiB: -4.32%
> gem:exec:fault:1MiB:forked: -5.66%
> gem:exec:fault:16MiB: -13.33%
> gem:exec:fault:16MiB:forked: -12.03%
> gem:exec:fault:256MiB: -15.28%
> gem:exec:fault:256MiB:forked: -16.98%
>
> (I was really hoping to be able to drop a patch!)
I think you've inlined sg_next() as well? That was the next thing I was
going to try with these ...
I'll post the version with inline sg_next, but I'm on holiday now so
won't be around until the end of the month.
.Dave.
next prev parent reply other threads:[~2016-05-20 0:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 15:19 [PATCH 1/3] drm/i915: refactor i915_gem_object_pin_map() Dave Gordon
2016-05-16 15:19 ` [PATCH 2/3] drm/i915: optimise i915_gem_object_map() for small objects Dave Gordon
2016-05-16 15:19 ` [PATCH 3/3] Introduce & use new lightweight SGL iterators Dave Gordon
2016-05-16 15:19 ` Dave Gordon
2016-05-17 10:34 ` Tvrtko Ursulin
2016-05-17 10:34 ` [Intel-gfx] " Tvrtko Ursulin
2016-05-17 12:05 ` Dave Gordon
2016-05-19 17:27 ` Chris Wilson
2016-05-20 0:13 ` Dave Gordon [this message]
2016-05-16 16:01 ` ✗ Ro.CI.BAT: failure for series starting with [1/3] drm/i915: refactor i915_gem_object_pin_map() Patchwork
2016-05-17 9:22 ` [PATCH 1/3] " Tvrtko Ursulin
2016-05-17 12:59 ` Dave Gordon
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=573E56AB.9040208@intel.com \
--to=david.s.gordon@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko.ursulin@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.