linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jordan <triplesquarednine@gmail.com>
To: pavel@pavlinux.ru
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: Thu, 5 Dec 2013 20:16:17 -0500	[thread overview]
Message-ID: <CAOcfFMwkBaqAFYKnt15JQgVn10F00UQrPa2HQi42P8=kawk3ug@mail.gmail.com> (raw)
In-Reply-To: <52A121F8.7010607@pavlinux.ru>

Hey Pavel

> Wow, I did not know, thanks. I until on 319.xx

I had wondered. lol. ~ because telling someone who is using nvidia-rt
>325xx that it doesn't work on rt is a bit odd. ;)  ... I thought you
must have been mistaken :)

take a look in kernel/conftest.sh (of nvidia installer/sources) - You
were mistaken because nvidia has changed some of the internals around
/ how their installer works. It actually appears they are making it
more RT friendly... Which is great because i (personally) have been
bugging them every couple of months about PREEMPT_RT_FULL :)

>>> 3. SFENCE need on SMP systems. Although, delay in 1000 nanoseconds - it's awful
>> Would you care to goto into more detail on this?
>
> https://www.kernel.org/doc/Documentation/memory-barriers.txt

Thanks, i'll have a read through + wait for some feedback from nvidia
in my thread.

jordan

  reply	other threads:[~2013-12-06  1:16 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
2013-12-05 23:43   ` jordan
2013-12-06  1:01     ` Pavel Vasilyev
2013-12-06  1:16       ` jordan [this message]
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='CAOcfFMwkBaqAFYKnt15JQgVn10F00UQrPa2HQi42P8=kawk3ug@mail.gmail.com' \
    --to=triplesquarednine@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pavel@pavlinux.ru \
    /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;
as well as URLs for NNTP newsgroup(s).