From: Eric Anholt <eric@anholt.net>
To: Peter Clifton <pcjc2@cam.ac.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: intel_prepare_render(intel); unhelpful?
Date: Mon, 01 Nov 2010 13:17:46 -0700 [thread overview]
Message-ID: <87wrowu7bp.fsf@pollan.anholt.net> (raw)
In-Reply-To: <1288641178.21440.61.camel@pcjc2lap>
[-- Attachment #1.1: Type: text/plain, Size: 762 bytes --]
On Mon, 01 Nov 2010 19:52:58 +0000, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> On Sun, 2010-10-31 at 20:54 -0700, Eric Anholt wrote:
>
> > Now, this version of the code has bothered me, since apps that execute
> > in one batchbuffer should end up getting overly penalized. See
> > intel-throttle-hack of my mesa tree for a possible fix.
>
> I like it! I still can't quite figure out what synchronisation issue I
> was running into with my app though. With a single wait_for_rendering /
> synchronisation per frame, I can't quite contrive how the GPU would get
> stalled at all during a sequence of consecutive frames.
I like it too, except for the whole "not just no performance
improvement, but actually penalty on everything I've tried" thing.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2010-11-01 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 1:15 intel_prepare_render(intel); unhelpful? Peter Clifton
2010-11-01 3:54 ` Eric Anholt
2010-11-01 19:20 ` Peter Clifton
2010-11-01 19:52 ` Peter Clifton
2010-11-01 20:17 ` Eric Anholt [this message]
[not found] ` <1288645484.2714.2.camel@pcjc2lap>
[not found] ` <874oc0203e.fsf@pollan.anholt.net>
2010-11-01 22:19 ` Peter Clifton
2010-11-02 15:40 ` 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=87wrowu7bp.fsf@pollan.anholt.net \
--to=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pcjc2@cam.ac.uk \
/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