From: Richard Cochran <richardcochran@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [RFC 0/1] Class driver for raw Ethernet packets
Date: Tue, 27 Sep 2011 19:04:00 +0200 [thread overview]
Message-ID: <20110927170358.GB6057@domain.hid> (raw)
In-Reply-To: <4E81FA08.4080106@domain.hid>
On Tue, Sep 27, 2011 at 06:30:00PM +0200, Jan Kiszka wrote:
> On 2011-09-27 18:26, Jan Kiszka wrote:
> > I was simply hoping to collect some new ideas how to address the driver
> > maintenance issue in a better way but without dropping key features
> > needed for RT networking. Something like "let's add generic RT channels
> > to Linux upstream drivers and then only patch them fit RTDM". Not sure
> > if that works, but it would come with a vision how to keep things more
> > maintainable.
>
> +this could be useful for other scenarios - on PREEMPT-RT.
(But PREEMPT-RT will make the whole kernel deterministic, right? ;)
Adding low-latency channels (eg. working against coalescing) will be a
very hard sell upstream.
Richard
next prev parent reply other threads:[~2011-09-27 17:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 11:02 [Xenomai-core] [RFC 0/1] Class driver for raw Ethernet packets Richard Cochran
2011-09-23 11:02 ` [Xenomai-core] [RFC 1/1] Add a class " Richard Cochran
2011-09-23 11:27 ` [Xenomai-core] [RFC 0/1] Class " Richard Cochran
2011-09-23 13:34 ` Peter Soetens
2011-09-23 13:50 ` Jan Kiszka
2011-09-26 11:41 ` Richard Cochran
2011-09-27 8:26 ` Jan Kiszka
2011-09-27 12:01 ` Richard Cochran
2011-09-27 12:20 ` Jan Kiszka
2011-09-27 15:10 ` Richard Cochran
2011-09-27 15:16 ` Jan Kiszka
2011-09-27 16:05 ` Richard Cochran
2011-09-27 16:26 ` Jan Kiszka
2011-09-27 16:30 ` Jan Kiszka
2011-09-27 17:04 ` Richard Cochran [this message]
2011-09-27 17:25 ` Jan Kiszka
2011-09-27 17:00 ` Richard Cochran
2011-09-27 17:25 ` Jan Kiszka
2011-09-28 8:16 ` Richard Cochran
2011-09-28 8:29 ` Jan Kiszka
2011-09-27 18:02 ` 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=20110927170358.GB6057@domain.hid \
--to=richardcochran@domain.hid \
--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.