All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Webb <jeff.webb@nta-inc.net>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] NVIDIA Drivers w/ Xenomai
Date: Tue, 22 Dec 2015 11:33:57 -0600	[thread overview]
Message-ID: <56798985.2090803@nta-inc.net> (raw)
In-Reply-To: <20151222155429.GS25177@csclub.uwaterloo.ca>

On 12/22/2015 09:54 AM, Lennart Sorensen wrote:
> On Tue, Dec 22, 2015 at 08:30:37AM +0100, Gilles Chanteperdrix wrote:
>> Last time I looked, NVIDIA drivers used some glue code to adapt to
>> the particular kernel for which they were compiled. This glue made
>> use of the standard macro local_irq_save/spin_lock_irqsave, etc...
>> So, compiling the NVIDIA driver with an I-pipe kernel worked, and so
>> did running Xenomai programs along side graphic applications. But
>> that was a long time ago. In any case, running the latency test
>> while your image processing program is running on the GPU should
>> allow you to find whether the driver is generating large latencies.
>
> OK, maybe it isn't as bad as I was led to believe in the past then.
>
> I suppose one could hope there are no interrupt disable calls in the
> nvidia binary blob directly.

I have experienced some high worst-case latencies when using the NVIDIA drivers along side Xenomai real-time code in the past.  The open source drivers seemed to be more well-behaved from a real-time point of view.  You may be able to get the closed-source drivers to work for your application, depending on your timing constraints and GPU feature usage.  As Gilles mentioned, you really should try running the latency test while putting the system (and GPU) under load.  As I remember, switching to another virtual console sometimes triggered some nasty behavior.

-Jeff



  reply	other threads:[~2015-12-22 17:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  0:22 [Xenomai] NVIDIA Drivers w/ Xenomai Eric Huang
2015-12-22  2:43 ` Lennart Sorensen
2015-12-22  7:30   ` Gilles Chanteperdrix
2015-12-22 15:54     ` Lennart Sorensen
2015-12-22 17:33       ` Jeff Webb [this message]
2015-12-23 12:48         ` Gilles Chanteperdrix
2015-12-22  7:37 ` Gilles Chanteperdrix

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=56798985.2090803@nta-inc.net \
    --to=jeff.webb@nta-inc.net \
    --cc=xenomai@xenomai.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 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.