RTP and Open Source FLEET

I haven’t seen a simple answer to this yet: is FLEET available for RTP,
and is it Open Source? If not now, will it be? We’ve used FLEET with
QNX4, but always wanted to change some of the time-outs to make it more
useful.

Dale

“Dale Paus” <dpaus@crisys.com> wrote in message
news:3A9D50C5.7E4B967D@crisys.com

I haven’t seen a simple answer to this yet: is FLEET available for RTP,

No it’s not

and is it Open Source?

I would be extremely surprise if it would. This is consider
core technology.

If not now, will it be?

I don’t think it will be done for RTPo (i’m not from QSSL)

We’ve used FLEET with QNX4, but always wanted to change
some of the time-outs to make it more useful.

Look at Net and netpool options.

Dale

Mario Charest <mcharest@void_zinformatic.com> wrote:

“Dale Paus” <> dpaus@crisys.com> > wrote in message
news:> 3A9D50C5.7E4B967D@crisys.com> …

I haven’t seen a simple answer to this yet: is FLEET available for RTP,

No it’s not

But there is a native QNX networking protocol to allow Send/Receive/Reply
accross the network.

and is it Open Source?

I would be extremely surprise if it would. This is considered
core technology.

But we do intend to release network driver development kits, and I
think these are currently in beta.

-David

QNX Training Services
dagibbs@qnx.com

Well, this doesn’t answer your question, but you might like to know that
most of the relevent timeouts for fleet are adjustable in QNX4. You
can control the behaviour of fleet via the driver timeout adjustments.
You can also customize the behaviour of QNX4 fleet via a netraw app that
controls the netmask. None of the above options are pretty (I sure hope
Qnet improves on this) but it can be done.

-----Original Message-----
From: Dale Paus [mailto:dpaus@crisys.com]
Posted At: Wednesday, February 28, 2001 11:26 AM
Posted To: os
Conversation: RTP and Open Source FLEET
Subject: RTP and Open Source FLEET


I haven’t seen a simple answer to this yet: is FLEET available for RTP,
and is it Open Source? If not now, will it be? We’ve used FLEET with
QNX4, but always wanted to change some of the time-outs to make it more
useful.

Dale

Dale Paus wrote:

I haven’t seen a simple answer to this yet: is FLEET available for RTP,
and is it Open Source? If not now, will it be? We’ve used FLEET with
QNX4, but always wanted to change some of the time-outs to make it more
useful.

Dale,

is PVM an ‘Open Source’ alternative for true parallel processing ??

See http://sourceforge.net/projects/pyqnx
http://www.epm.ornl.gov/pvm/pvm_home.html
or if JAVA is an option
http://www.mathcs.emory.edu/harness/HARNESS/proto.html

Armin

Rennie Allen <RAllen@csical.com> wrote:

Well, this doesn’t answer your question, but you might like to know that
most of the relevent timeouts for fleet are adjustable in QNX4. You
can control the behaviour of fleet via the driver timeout adjustments.

Actually you can control a variety of different things:
– packet timeouts with Net.driver options -f -n -t
– failed network retry with Net option -t
– nameloc polling frequency & style with options -p -s -S -Z
– vc tear-down polling and timeouts with netpoll (-i -n -p -r,
all affect this, as that is all netpoll controls)

-David

You can also customize the behaviour of QNX4 fleet via a netraw app that
controls the netmask. None of the above options are pretty (I sure hope
Qnet improves on this) but it can be done.

I don’t know about not pretty – maybe not, but together they do give you
a lot of tuneability as to how the QNX FLEET network behaves.

-David

QNX Training Services
dagibbs@qnx.com

Thanks for the links, Armin. HARNESS has some potential as a model for us,
but first I need to make the networking reliable and deterministic. FLEET
gets us part way there, but the time it takes to reconfigure under fault
conditions kills its usefulness to use. In another response, Rennie has
pointed us to some options we may not be fully exploiting; I’ll have to
consult with our resident prop-heads. If we come up with anything, we’ll let
everyone know.

Dale




Armin Steinhoff wrote:

Dale Paus wrote:

I haven’t seen a simple answer to this yet: is FLEET available for RTP,
and is it Open Source? If not now, will it be? We’ve used FLEET with
QNX4, but always wanted to change some of the time-outs to make it more
useful.

Dale,

is PVM an ‘Open Source’ alternative for true parallel processing ??

See > http://sourceforge.net/projects/pyqnx
http://www.epm.ornl.gov/pvm/pvm_home.html
or if JAVA is an option
http://www.mathcs.emory.edu/harness/HARNESS/proto.html

Armin

David Gibbs wrote:

Mario Charest <mcharest@void_zinformatic.com> wrote:

“Dale Paus” <> dpaus@crisys.com> > wrote in message
news:> 3A9D50C5.7E4B967D@crisys.com> …

I haven’t seen a simple answer to this yet: is FLEET available for RTP,

No it’s not

But there is a native QNX networking protocol to allow Send/Receive/Reply
accross the network.

and is it Open Source?

I would be extremely surprise if it would. This is considered
core technology.

But we do intend to release network driver development kits, and I
think these are currently in beta.

Yes, the driver kits are now available, and we’re grateful for that. But that
won’t help us make Qnet any more responsive. I thought the “restricted Open
Source” approach was to open everything except the kernal? Surely you’re not
going to tell us that Qnet is part of the kernal?? :wink: (and sorry about
calling you “Shirley”)


Dale



-David

QNX Training Services
dagibbs@qnx.com

Hmmmmm… This sounds interesting. I’ll go do some more digging.

Thanks!


Dale



David Gibbs wrote:

Rennie Allen <> RAllen@csical.com> > wrote:
Well, this doesn’t answer your question, but you might like to know that
most of the relevent timeouts for fleet are adjustable in QNX4. You
can control the behaviour of fleet via the driver timeout adjustments.

Actually you can control a variety of different things:
– packet timeouts with Net.driver options -f -n -t
– failed network retry with Net option -t
– nameloc polling frequency & style with options -p -s -S -Z
– vc tear-down polling and timeouts with netpoll (-i -n -p -r,
all affect this, as that is all netpoll controls)

-David

You can also customize the behaviour of QNX4 fleet via a netraw app that
controls the netmask. None of the above options are pretty (I sure hope
Qnet improves on this) but it can be done.

I don’t know about not pretty – maybe not, but together they do give you
a lot of tuneability as to how the QNX FLEET network behaves.

-David

QNX Training Services
dagibbs@qnx.com

You can also customize the behaviour of QNX4 fleet via a netraw app
that
controls the netmask. None of the above options are pretty (I sure
hope
Qnet improves on this) but it can be done.

I don’t know about not pretty – maybe not, but together they do give
you
a lot of tuneability as to how the QNX FLEET network behaves.

If you want fine grained control, you certainly aren’t going to get away
from how many different types of timeouts there are, but it would
certainly
be a lot nicer if they were all in one place.

Rennie

Previously, Dale Paus wrote in qdn.public.qnxrtp.os:

Surely you’re not
going to tell us that Qnet is part of the kernal?? > :wink:

I’ve never heard QSSL say that they were going to release
source for everything but the kernel. The term they used
for what would not be released was “core technologies”.
I think we can safely assume that this includes most of the
kernel and source for which QSSL needed an NDA. Beyond that
I’d guess the Photon kernel is a likely candidate.


Mitchell Schoenbrun --------- maschoen@pobox.com