From: Mike Galbraith <efault@gmx.de>
To: valdis.kletnieks@vt.edu
Cc: Chris Jones <chrisjones@spin.net.au>,
linux-kernel@vger.kernel.org, david@lang.hm
Subject: Re: Gaming and the kernel
Date: Sat, 04 Aug 2012 07:38:56 +0200 [thread overview]
Message-ID: <1344058736.9497.5.camel@marge.simpson.net> (raw)
In-Reply-To: <1344055742.6739.40.camel@marge.simpson.net>
On Sat, 2012-08-04 at 06:49 +0200, Mike Galbraith wrote:
> On Sat, 2012-08-04 at 00:12 -0400, valdis.kletnieks@vt.edu wrote:
> > On Sat, 04 Aug 2012 10:51:49 +1000, Chris Jones said:
> >
> > > documentation, hopefully things will work out. And this might actually
> > > be the kick in the rear-end that AMD and NVIDIA need to get into gear
> > > and start developer some useful and Windows equivalent hardware drivers
> > > for ALL their cards for Linux.
> >
> > The truly ironic part is that the current NVidia binary blob driver that
> > everybody dislikes so much *IS* the "Windows equivalent" driver (in
> > fact, it's the same driver, with a Linux shim layer wrapped around it).
>
> Hm.. so windows can be kept in kernel for a full second of IPI blasting
> all cores too. That driver seems to work very nicely once things are
> running, but whatever the heck it does when you first fire up rendering
> is.. something to keep far far away from realtime tasks :)
That seems to have gotten about a ton better. Worst just measured with
295.53 under 3.0-rt58 was 7.7ms, with typical being < 1ms.
-Mike
prev parent reply other threads:[~2012-08-04 5:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 22:12 Gaming and the kernel Chris Jones
2012-08-03 22:46 ` Cruz Julian Bishop
[not found] ` <501C545C.40601@gmail.com>
2012-08-04 0:25 ` Chris Jones
2012-08-04 0:32 ` david
2012-08-04 0:51 ` Chris Jones
2012-08-04 4:12 ` valdis.kletnieks
2012-08-04 4:49 ` Mike Galbraith
2012-08-04 5:38 ` Mike Galbraith [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=1344058736.9497.5.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=chrisjones@spin.net.au \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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