All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Keith Packard <keithp@keithp.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] [RFC] drm/i915: read-read semaphore optimization
Date: Tue, 13 Dec 2011 14:49:49 -0800	[thread overview]
Message-ID: <4EE7D68D.1090803@bwidawsk.net> (raw)
In-Reply-To: <86k460ig3j.fsf@sumi.keithp.com>

On 12/13/2011 08:36 AM, Keith Packard wrote:
> On Tue, 13 Dec 2011 17:01:33 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> 
>> - or remove it all and invalidate/flush unconditionally.
> 
> Eric and I were chatting yesterday about trying this -- it seems like
> we'd be able to dramatically simplify the kernel module by doing this,
> and given how much flushing already occurs, I doubt we'd see any
> significant performance difference, and we'd save a pile of CPU time,
> which might actually improve performance.


Would we want to keep domain tracking if the HW worked correctly and we
didn't have to always flush. It seems like a shame to just gut the code
if it actually could offer a benefit on future generations.

I know Daniel has the same idea about gutting it...

Ben

  reply	other threads:[~2011-12-13 22:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13  3:52 [PATCH] [RFC] drm/i915: read-read semaphore optimization Ben Widawsky
2011-12-13  9:49 ` Chris Wilson
2011-12-13 16:01   ` Daniel Vetter
2011-12-13 16:36     ` Keith Packard
2011-12-13 22:49       ` Ben Widawsky [this message]
2011-12-13 23:22         ` Keith Packard
2011-12-14  1:09         ` Eric Anholt
2011-12-14  3:25           ` Keith Packard
2011-12-13 16:59     ` Chris Wilson
2011-12-13 17:22 ` Eric Anholt
2011-12-13 18:36   ` Ben Widawsky
2012-01-16 21:50     ` Daniel Vetter
2012-01-16 22:20       ` Ben Widawsky
2012-01-17  3:41         ` Eric Anholt
2012-01-17 10:15         ` Daniel Vetter
2012-01-17 17:55           ` Eric Anholt

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=4EE7D68D.1090803@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.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.