All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] RT OS Selection advice for parallel processing
Date: Thu, 03 Feb 2011 12:49:40 +0100	[thread overview]
Message-ID: <4D4A9654.80402@domain.hid> (raw)
In-Reply-To: <4D4A957B.6050907@domain.hid>

Jan Kiszka wrote:
> On 2011-02-03 12:27, Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> On 2011-02-03 12:04, Gilles Chanteperdrix wrote:
>>>> Jan Kiszka wrote:
>>>>> [ And, personally, I don't trust the NVIDIA driver a lot. But that might
>>>>> be influenced by the fact that latest versions lock up my notebook
>>>>> regularly after resume and that I filed another obvious locking issue of
>>>>> the compilable driver stub around mmap_sem without any response from the
>>>>> vendor. ]
>>>> Some colleague of mine is using the NVIDIA driver (through the opengl
>>>> mapping, not CUDA/VDPAU, whatever) on high-end NVIDIA boards in a non RT
>>>> situation. he definitely observed some huge latencies not due to
>>>> scheduling issues, when uploading textures to the GPU. We are talking
>>>> tens of milliseconds here.
>>> Ugh, tens of milliseconds is heavy, more than I would expect from
>>> wbinvd. OTOH, uploading textures may involve mapping the RAM that
>>> contains them for the GPU. To exclude that as source, he could try
>>> instrumenting CACHE_FLUSH() (in nv-linux.h).
>> No, it really looks like a bug in the blob. Of course the 40ms is a spot
>> from time to time, usually, the upload is really fast.
> 
> Unless it's a stall on the PCI bus, the blob should leaves some traces
> in ftrace.

I am talking about the kernel-space blob. ftrance does just show that
the ioctl has been submitted.



-- 
					    Gilles.


  reply	other threads:[~2011-02-03 11:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03  8:57 [Xenomai-help] RT OS Selection advice for parallel processing Rudolf Meijering
2011-02-03 10:35 ` Jan Kiszka
2011-02-03 11:04   ` Gilles Chanteperdrix
2011-02-03 11:24     ` Jan Kiszka
2011-02-03 11:27       ` Gilles Chanteperdrix
2011-02-03 11:46         ` Jan Kiszka
2011-02-03 11:49           ` Gilles Chanteperdrix [this message]
2011-02-03 12:50             ` Jan Kiszka
2011-02-03 13:21               ` Gilles Chanteperdrix
2011-02-04 13:33                 ` Rudolf Meijering
2011-02-04 22:15                   ` Gilles Chanteperdrix
2011-02-12 18:13                   ` Richard Cochran

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=4D4A9654.80402@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --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.