From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: read/write IOCTLs
Date: Sat, 2 Apr 2011 08:16:47 -0700 [thread overview]
Message-ID: <20110402151647.GA27656@snipes.kumite> (raw)
In-Reply-To: <b7da2f$qure4k@fmsmga001.fm.intel.com>
On Sat, Apr 02, 2011 at 07:46:31AM +0100, Chris Wilson wrote:
>
> But perhaps we do need to reconsider the performance aspect. intel_gpu_top
> samples the ring HEAD and TAIL at around 10KHz and forcing gt-wake is
> about 50 microseconds... I hope I'm mistaken, because even batched that is
> doomed. Ben, do you mind checking that thought experiment with a little
> hard fact?
I can get some numbers for it... but I'd like to further the discussion
a bit since I have to go to the office to get a SNB, and typing is
easier than doing that right now :).
I too think we might be doomed. At the very least we have the
POSTING_READ, which is expensive. The udelays may or may not actually
occur (I'll find out). Let's not forget too that we do fix other tools,
not just intel_gpu_top, and those tools don't poll, and don't care about
timing (granted they're mostly less interesting too).
I think what we really need to try to defer the forcewake_put, as well
as something like the last patch I sent
<1301105269-23970-2-git-send-email-ben@bwidawsk.net> to remove the need
to protect force_wake_get with struct_mutex, and keep a refcount. I'd
rather get the current stuff accepted, port the tools, and then make
improvements to the performance. However if you feel the order must be
another way, I can work with that.
> -Chris
>
Thanks.
Ben
next prev parent reply other threads:[~2011-04-02 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 1:31 [PATCH] drm/i915: read/write IOCTLs Ben Widawsky
2011-04-01 1:39 ` [PATCH v2] " Ben Widawsky
2011-04-01 23:54 ` Read/Write IOCTL compromise Ben Widawsky
2011-04-06 21:38 ` No more read/write ioctls Ben Widawsky
2011-04-08 17:10 ` Eric Anholt
2011-04-08 17:29 ` Chris Wilson
2011-04-01 23:54 ` [PATCH v3 1/2] drm/i915: read/write ioctls for userspace Ben Widawsky
2011-04-04 17:14 ` Chris Wilson
2011-04-05 1:30 ` Read/Write ioctls Ben Widawsky
2011-04-05 1:30 ` [PATCH v4] drm/i915: read/write ioctls for userspace Ben Widawsky
2011-04-01 23:54 ` [PATCH v3 2/2] drm/i915: debugfs for register write taint Ben Widawsky
2011-04-01 6:36 ` [PATCH] drm/i915: read/write IOCTLs Chris Wilson
2011-04-01 7:06 ` Ben Widawsky
2011-04-01 7:32 ` Chris Wilson
2011-04-01 18:51 ` Eric Anholt
2011-04-02 6:46 ` Chris Wilson
2011-04-02 15:16 ` Ben Widawsky [this message]
2011-04-04 1:35 ` Ben Widawsky
2011-04-04 7:36 ` Chris Wilson
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=20110402151647.GA27656@snipes.kumite \
--to=ben@bwidawsk.net \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).