From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
"Jesse Barnes" <jbarnes@virtuousgeek.org>,
dri-devel@lists.sourceforge.net,
"Thomas Hellström" <unichrome@shipmail.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-rt4: via DRM errors
Date: Fri, 25 Nov 2005 20:06:12 +0000 [thread overview]
Message-ID: <1132949172.7987.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1132946629.20390.51.camel@mindpipe>
On Gwe, 2005-11-25 at 14:23 -0500, Lee Revell wrote:
> On Fri, 2005-11-25 at 20:13 +0100, Arjan van de Ven wrote:
> > of course sometimes having less but more coarse locks is actually
> > faster. Taking/dropping a lock is not free. far from it.
>
> True but couldn't it be a problem for devices like unichrome where you
> have 3D and MPEG acceleration and they have to play nice? It just seems
> like there may have been an implicit assumption that devices only
> support one type of hardware acceleration.
Not really. The DRI locking is what the driver makes of it. Generally
GPUs are internally very coarse grained and don't like doing different
jobs at the same time anyway.
The nearest thing I think to look at it as would be futex locks, and DRI
could probably use futex locks with some glue for the X authentication
side of things. However futex locks are not in FreeBSD and may never be
(IBM patent questions for non-GPL), and DRI predates futexes by a large
margin.
next prev parent reply other threads:[~2005-11-25 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 4:53 2.6.14-rt4: via DRM errors Lee Revell
2005-11-24 9:52 ` Thomas Hellström
2005-11-24 10:44 ` Dave Airlie
2005-11-24 10:49 ` Lee Revell
2005-11-24 12:50 ` Thomas Hellström
2005-11-24 15:31 ` Jesse Barnes
2005-11-24 16:04 ` Thomas Hellström
2005-11-25 19:05 ` Lee Revell
2005-11-25 19:13 ` Arjan van de Ven
2005-11-25 19:23 ` Lee Revell
2005-11-25 20:06 ` Alan Cox [this message]
2005-11-25 16:24 ` Alan Cox
2005-11-25 19:21 ` Lee Revell
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=1132949172.7987.2.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=unichrome@shipmail.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