From: Pavel Vasilyev <pavel@pavlinux.ru>
To: jordan <triplesquarednine@gmail.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: Solving Nvidia (blob) latency spikes + convert (nvidia's) semaphores into mutexes patches for 331.20 [patches and links provided]
Date: Fri, 06 Dec 2013 03:04:29 +0400 [thread overview]
Message-ID: <52A1067D.8070009@pavlinux.ru> (raw)
In-Reply-To: <CAOcfFMzTXoSBJm8Rss6XKugc5knfDfdNaYT34bV=N2qcqeKkeg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
06.12.2013 01:20, jordan пишет:
> Hey list,
>
> I have been experimenting with the nvidia blob, monitoring behavior /
> latencies, etc. Through some experimentation, googling/research and
> looking over previous nvidia-rt/compat patches from all over the
> interwebs; I've put together a few patches for the latest
> nvidia-331.20 driver.
1. Blob after 325.xx.xx does not compile and does not work with our RT patches!
2. Nvidia developers specifically inserted function WBINVD to slowly work? :)
3. SFENCE need on SMP systems. Although, delay in 1000 nanoseconds - it's awful
4. Do you really think, that mutex_lock/unlock more realtime than up/down?
--
Pavel.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-05 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 21:20 Solving Nvidia (blob) latency spikes + convert (nvidia's) semaphores into mutexes patches for 331.20 [patches and links provided] jordan
2013-12-05 23:04 ` Pavel Vasilyev [this message]
2013-12-05 23:43 ` jordan
2013-12-06 1:01 ` Pavel Vasilyev
2013-12-06 1:16 ` jordan
2013-12-17 18:10 ` Glenn Elliott
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=52A1067D.8070009@pavlinux.ru \
--to=pavel@pavlinux.ru \
--cc=linux-rt-users@vger.kernel.org \
--cc=triplesquarednine@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.