All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Reinstate order of operations in {intel, logical}_ring_begin()
Date: Tue, 16 Jun 2015 13:24:31 +0100	[thread overview]
Message-ID: <20150616122431.GC11933@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20150616121855.GT23637@phenom.ffwll.local>

On Tue, Jun 16, 2015 at 02:18:55PM +0200, Daniel Vetter wrote:
> Maybe someone should look at per-buffer locks before trying to split up
> the low-level hw locks ;-)

Per-vm then per-buffer. Adding more locked operations to execbuf is
scary though, with some workloads perf highlights the cost of the atomic
for an uncontested mutex as being where the majority of the time is
going.

At this point I am questing perf, but it is the last remaining locked
instruction in that path...
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-06-16 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 18:51 [PATCH] drm/i915: Reinstate order of operations in {intel, logical}_ring_begin() Dave Gordon
2015-06-13 20:16 ` shuang.he
2015-06-15  9:15 ` Chris Wilson
2015-06-15 18:11   ` Dave Gordon
2015-06-15 20:41     ` Chris Wilson
2015-06-16 11:03       ` Dave Gordon
2015-06-16 12:18         ` Daniel Vetter
2015-06-16 12:24           ` Chris Wilson [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=20150616122431.GC11933@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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 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.