From: Jan Kiszka <jan.kiszka@domain.hid>
To: Rudolf Meijering <rudolf@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RT OS Selection advice for parallel processing
Date: Thu, 03 Feb 2011 11:35:25 +0100 [thread overview]
Message-ID: <4D4A84ED.7030604@domain.hid> (raw)
In-Reply-To: <AANLkTikSnhe5fnSLQm7eSOh9R7YA2cJ=m78n+S3kpW9K@mail.gmail.com>
On 2011-02-03 09:57, Rudolf Meijering wrote:
> Hi,
>
> We are in the process of developing a non-tracking safety Radar and would
> really appreciate some guidance in selecting a real-time operating system
> especially with the aim of offloading processing to a GPU. Can anyone share
> their experience with real-time GPU offloading on either Xenomai or Realtime
> Linux (PREEMPT_RT patch)? I have read reports on 900us delays with Nvidia
> graphics drivers, has this been resolved?
The NVIDIA CUDA bits cause problems to any RT scenario when you trigger
DMA memory allocations/releases, thus mapping during runtime (wbinvd). I
can't tell you details, but my colleagues somehow solved this for our
non-RT GPU offloading tasks although we received no information which
APIs can trigger the problematic code paths (the binary blob is in the
loop so only NVIDIA can tell).
>
> Background:
> The application basically requires the radar to output a disable
> signal, within 100ms, when an object is detected. Radar data is received
> every 1 ms and processed.
>
> Platform: x86_64, most likely Intel i7 CPU
> Total processing latency: 100ms
> Interrupt frequency: 1KHz
>
> From what I can read both Xenomai and Realtime Linux should easily meet
> these requirements, but what about RT GPU support?
Given the fact that the NVIDIA driver is neither designed nor properly
tested against PREEMPT-RT (you need extra hacks to make it work), I'm a
bit skeptical that you can expect any RT properties when trying to use
the GPU in time critical paths. No one (except maybe the vendor) knows
the timing of the GPU hardware and software bits under critical load
scenarios.
If "just" that 100 ms is the deadline and you measure over a long time
that your GPU tasks always complete much earlier, you may argue that
it's /probably/ safe. But if you need to certify this, well...
[ 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. ]
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-02-03 10:35 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 [this message]
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
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=4D4A84ED.7030604@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=rudolf@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.