From: Nick Garnett <nickg@cygnus.co.uk>
To: Stuart Hughes <sehughes@zentropix.com>
Cc: elix@sourceware.cygnus.com
Subject: Re: RTLinux workshop and EL/IX press coverage on EETimes
Date: Thu, 23 Dec 1999 04:23:00 -0000 [thread overview]
Message-ID: <po902lc0cq.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <3861F6B9.1FA6C63A@zentropix.com>
Stuart Hughes <sehughes@zentropix.com> writes:
> You're right, if a realtime task made a call to a Linux kernel service,
> is not longer running at a realtime priority and this would need to be
> made very clear. One of the ideas we had was to reserve a group of
> priorities that would be 'kernel priority', and say that any RT task
> calling these services must run at kernel priority, to enforce this we
> would need some checking (maybe simply forcing the need to link to a
> library). At the moment, this is only an idea, but I would love to see
> some kind of transparent access to the Linux kernel from RT to make the
> programmer feel that he/she is developing in a coherent environment.
>
I think this is important. The "two level" model that currently exists
is, as someone on /. said yesterday, a bit of a hack. The more that
can be done to produce a single seamless programmer model the better.
> As you mention, the C library is also a problem and there is a need for
> (and we have been exploring) a libc_rt.a library. Already some brave
> people have been linking in some of the static libraries into their
> applications (libm.a is common). Generally this works, but at the end
> of that day you need to know what you are letting yourself in for.
>
> BTW Nick, can you let me have another e-mail address for you
> (nickg@cygnus.co.uk has been bouncing).
>
Really? That is my canonical address and should work. You can try
nickg@cygnus.com, but that is really just a forward to my .uk address.
It may be that you are accidentally being zapped by out spam filter.
I have just talked to our sysadmin and that is exactly what is
happening. It appears that your IP address is in a range that someone
sometime decided we didn't like. Probably as a result of spam from
another user of your ISP. It should be fixed now. If you get any more
bounces, let me know.
--
Nick Garnett mailto:nickg@cygnus.co.uk
Cygnus Solutions, UK http://www.cygnus.co.uk
prev parent reply other threads:[~1999-12-23 4:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-22 8:02 Paul Beskeen
1999-12-22 8:21 ` Stuart Hughes
1999-12-22 8:51 ` Nick Garnett
1999-12-22 9:20 ` Mark Johannes
1999-12-22 10:16 ` Nick Garnett
1999-12-22 9:56 ` Stuart Hughes
1999-12-22 10:26 ` Nick Garnett
1999-12-23 3:39 ` Stuart Hughes
1999-12-23 4:23 ` Nick Garnett [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=po902lc0cq.fsf@balti.cygnus.co.uk \
--to=nickg@cygnus.co.uk \
--cc=elix@sourceware.cygnus.com \
--cc=sehughes@zentropix.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).