All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: emin ak <eminak71@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] gigabit rate packet processing with xenomai
Date: Thu, 30 Mar 2006 23:01:31 +0200	[thread overview]
Message-ID: <442C472B.2090300@domain.hid> (raw)
In-Reply-To: <2cf1ee820603300724w1335df09nf4d2abb0755107d5@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

emin ak wrote:
> Dear All;
> Thanks for the answers firstly.
> I'am using linux (and also xenomai ) for a powerpc (PQ3/MPC8540) and
> will use on chip gigabit ethernet controller (tsec) that is not
> supported on rt-net yet (maybe untill I'll write one:)
> In my opinion and my basic tests shows that context switch times and
> system call latecies in linux decrease user space performance
> significally even with highest RT_FIFO priority and this reasons
> prevent my gigabit rate data processing in user space.
> I think I'll firstly choose un-deterministical way, write a realtime
> user space thread that process the data coming from linux ethernet
> driver, if it fails, I'll adapt the driver for rt-net or wait for the
> up-coming realtime-preemptive patch.

If you can live with a certain amount of deadline misses, this is
probably the most reasonable approach. And preempt-rt will further
improve the quality of service but will still not be able to /guarantee/
networking latencies (the network stack is not explicitly included in
the latency improvements under preempt-rt, resource allocation remains
nondeterministic).

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

      reply	other threads:[~2006-03-30 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28  8:09 [Xenomai-help] gigabit rate packet processing with xenomai emin ak
2006-03-28 16:38 ` Jan Kiszka
2006-03-30 15:24   ` emin ak
2006-03-30 21:01     ` Jan Kiszka [this message]

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=442C472B.2090300@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=eminak71@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.