From: Thomas Hellstrom <thellstrom@vmware.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: "airlied@redhat.com" <airlied@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/1][-next] drm/radeon: Move over to the ttm execbuf utilities
Date: Wed, 17 Nov 2010 20:56:38 +0100 [thread overview]
Message-ID: <4CE43376.6020500@vmware.com> (raw)
In-Reply-To: <AANLkTingrruGmewT9FDMiCPCtcEav-Z1pPo874dBUfB3@mail.gmail.com>
On 11/17/2010 08:11 PM, Jerome Glisse wrote:
> On Wed, Nov 17, 2010 at 7:38 AM, Thomas Hellstrom<thellstrom@vmware.com> wrote:
>
>> The patch is compile-tested ony and not very intrusive. It should be applied
>> on top of the latest TTM patches.
>>
>> Besides reduced CPU-usage on SMP kernels, there is the benefit of using
>> shared code. Will also ease implementation of concurrent CS due to the
>> deadlock prevention mechanisms.
>>
>> If time allows, I'll write a patch to do the same on Novueau, although
>> Novueau does things a little differently than the other TTM-aware drivers.
>>
>>
>>
> Test on on rs780 and it seems to work properly, but i haven't really
> stress test it beside few games. I see no perf or CPU use improvement
> but it could very well be hidden by others cost.
>
Probably. I would have expected that a CPU-bound app, for example ipers
if running at 100% CPU (before the patch) would've seen some frame rate
improvements..
> Note that we can't really have concurrent cs due to the way checking
> work. Anyway you could add my reviewed by.
>
Thanks, Jerome.
/Thomas
> Reviewed-by: Jerome Glisse<jglisse@redhat.com>
> Tested-by: Jerome Glisse<jglisse@redhat.com>
>
prev parent reply other threads:[~2010-11-17 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 12:38 [PATCH 0/1][-next] drm/radeon: Move over to the ttm execbuf utilities Thomas Hellstrom
2010-11-17 12:38 ` [PATCH 1/1] drm/radeon: Use " Thomas Hellstrom
2010-11-17 19:11 ` [PATCH 0/1][-next] drm/radeon: Move over to " Jerome Glisse
2010-11-17 19:56 ` Thomas Hellstrom [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=4CE43376.6020500@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox