QNX Native Networking

Is QNX native networking, “FLEET”, an acronym?

I have not seen this anywhere in docs or on the web.

Anyone know what it stands for?

\

  • GF

A unique feature of the QNX realtime operating system, FLEET creates a
single homogeneous set of resources that you can access transparently,
anywhere throughout the network. FLEET is an ultralight, high-speed
networking protocol. Its innovative and feature-rich design turns
network-connected machines into a single logical supercomputer. Because
FLEET is built on the message-passing architecture of the QNX OS, it offers
the ultimate in flexibility. FLEET delivers:

a… Fault-tolerant networking
b… Load-balancing on the fly
c… Efficient performance
d… Extensible architecture
e… Transparent distributed processing

Fault-tolerant networking
If a cable or network card in one network fails, FLEET automatically
re-routes data through another network. This happens on the fly, without
involving application software, giving you automatic network
fault-tolerance.

Load-balancing on the fly
Network throughput is normally limited by the speed of your computer and
network hardware. With FLEET, data can be transmitted over multiple networks
simultaneously, allowing you to double, triple, or even quadruple your
network bandwidth and throughput by placing multiple network cards in each
computer and connecting them with separate cables. You can even mix
different types of network cards (e.g. Ethernet, FDDI) in the same machine.

Efficient performance
FLEET network drivers are built to make the most of your networking
hardware. For example, when sending large blocks of data over an Ethernet
network from one process to another, you get impressive throughput:

Network No. of client processes Throughput
10 Mbit Ethernet 1 1.1 Mbytes/sec
100 Mbit Ethernet 1 7.5 Mbytes/sec
(limited by network card)

Extensible architecture
Thanks to FLEET, a QNX network gives you unsurpassed flexibility. Networking
processes are architecturally distinct from the OS, allowing you to start
and stop a networked node at any time. This means you can add nodes to your
network or remove them dynamically without reconfiguring your system. And,
thanks to automatic network bridging, you can add different physical
networks to your LAN as well.

Transparent distributed processing
FLEET’s networking processes are deeply integrated into the heart of
message-passing and process-management primitives, making local and
network-wide IPC one and the same. Since IPC is network transparent, a
network of individual PCs appears as a single, seamless supercomputer. The
end result? You never need to modify your applications to communicate across
the network.

“Gordon Freeman” <gfreeman@bigfoot.com> wrote in message
news:c9nljm$mnm$1@inn.qnx.com

Is QNX native networking, “FLEET”, an acronym?

I have not seen this anywhere in docs or on the web.

Anyone know what it stands for?

\

  • GF

Hi, everyone
I’m a newer to QNX. When I built a project under IDE 6.2.1 the system seems
can not find a lib file: …/arm/a-le-g/libmax533_dtoa.a. But I found the
file is in a different directory: …/arm/a-le/libmax533_dtoa.a. Should I set
some environment paras somewhere? Here are the build messages:

make CPULIST=x86/arm all
make -j 1 -Carm -fMakefile all && make -j 1 -Cx86 -fMakefile all
make[1]: Entering directory /home/mjkadour/workspace/max533_dtoa/arm' make -j 1 -Co-le -fMakefile all && make -j 1 -Co-le-g -fMakefile all make[2]: Entering directory /home/mjkadour/workspace/max533_dtoa/arm/o-le’
make[2]: Nothing to be done for all'. make[2]: Leaving directory /home/mjkadour/workspace/max533_dtoa/arm/o-le’
make[2]: Entering directory
`/home/mjkadour/workspace/max533_dtoa/arm/o-le-g’
/bin/rm -f /home/mjkadour/workspace/max533_dtoa/arm/o-le-g/max533_dtoa_g
/usr/bin/qcc -Vgcc_ntoarm -Wl,–no-keep-memory -o/home/mjkadour/workspac
e/max533_dtoa/arm/o-le-g/max533_dtoa_g

ax533_dtoa.o -L. -L/armle/lib -L/armle/usr/lib -Bstatic -l/home/mjkad
our/workspace/max533_dtoa/…/max533_dtoa_lib/arm/a-le-g/libmax533_dtoa.a
-l/home/mjkadour/workspace/max533_dtoa/…/sa1110_gpio_lib/arm/a-le-g/libsa11
10_gpio.a -Bdynamic -EL -g
/usr/bin/ntoarm-ld: cannot open
/home/mjkadour/workspace/max533_dtoa/…/max533_dtoa_lib/arm/a-le-g/libmax533
_dtoa.a: No such file or directory
cc: /usr/bin/ntoarm-ld error 1
make[2]: *** [/home/mjkadour/workspace/max533_dtoa/arm/o-le-g/max533_dtoa_g]
Error 1
make[1]: *** [all] Error 2
make: *** [all] Error 2
make[2]: Leaving directory /home/mjkadour/workspace/max533_dtoa/arm/o-le-g' make[1]: Leaving directory /home/mjkadour/workspace/max533_dtoa/arm



Thanks in advance!

Jack Li
Electronic Engineer
905-673-8501 Ext.245
Cardiogenics Inc.
6295 Northam Drive, Unit 8
Mississauga, Ontario, Canada
L4V 1H8

Gordon Freeman wrote:

Is QNX native networking, “FLEET”, an acronym?

I have not seen this anywhere in docs or on the web.

Anyone know what it stands for?

it stands for QNX4 based networking … it is not applicable for QNX6

Regards

Armin

  • GF

Is this a publicitary ng, or a technical one?

“Lawrence R. Sweet” wrote:

A unique feature of the QNX realtime operating system, FLEET creates a
single homogeneous set of resources that you can access transparently,
anywhere throughout the network. FLEET is an ultralight, high-speed
networking protocol. Its innovative and feature-rich design turns
network-connected machines into a single logical supercomputer. Because
FLEET is built on the message-passing architecture of the QNX OS, it offers
the ultimate in flexibility. FLEET delivers:

a… Fault-tolerant networking
b… Load-balancing on the fly
c… Efficient performance
d… Extensible architecture
e… Transparent distributed processing

Fault-tolerant networking
If a cable or network card in one network fails, FLEET automatically
re-routes data through another network. This happens on the fly, without
involving application software, giving you automatic network
fault-tolerance.

Load-balancing on the fly
Network throughput is normally limited by the speed of your computer and
network hardware. With FLEET, data can be transmitted over multiple networks
simultaneously, allowing you to double, triple, or even quadruple your
network bandwidth and throughput by placing multiple network cards in each
computer and connecting them with separate cables. You can even mix
different types of network cards (e.g. Ethernet, FDDI) in the same machine.

Efficient performance
FLEET network drivers are built to make the most of your networking
hardware. For example, when sending large blocks of data over an Ethernet
network from one process to another, you get impressive throughput:

Network No. of client processes Throughput
10 Mbit Ethernet 1 1.1 Mbytes/sec
100 Mbit Ethernet 1 7.5 Mbytes/sec
(limited by network card)

Extensible architecture
Thanks to FLEET, a QNX network gives you unsurpassed flexibility. Networking
processes are architecturally distinct from the OS, allowing you to start
and stop a networked node at any time. This means you can add nodes to your
network or remove them dynamically without reconfiguring your system. And,
thanks to automatic network bridging, you can add different physical
networks to your LAN as well.

Transparent distributed processing
FLEET’s networking processes are deeply integrated into the heart of
message-passing and process-management primitives, making local and
network-wide IPC one and the same. Since IPC is network transparent, a
network of individual PCs appears as a single, seamless supercomputer. The
end result? You never need to modify your applications to communicate across
the network.

“Gordon Freeman” <> gfreeman@bigfoot.com> > wrote in message
news:c9nljm$mnm$> 1@inn.qnx.com> …
Is QNX native networking, “FLEET”, an acronym?

I have not seen this anywhere in docs or on the web.

Anyone know what it stands for?

\

  • GF

“Gordon Freeman” <gfreeman@bigfoot.com> wrote in message
news:c9nljm$mnm$1@inn.qnx.com

Is QNX native networking, “FLEET”, an acronym?

Yes it is, but I don’t remember what it is.

I think the F was for Fast the L for Light.

I have not seen this anywhere in docs or on the web.

Anyone know what it stands for?

\

  • GF

Mario Charest wrote:

“Gordon Freeman” <> gfreeman@bigfoot.com> > wrote in message
news:c9nljm$mnm$> 1@inn.qnx.com> …

Is QNX native networking, “FLEET”, an acronym?



Yes it is, but I don’t remember what it is.

I think the F was for Fast the L for Light.

F Fault tolerant
L Load balancing
E Efficient
E Extensible
T Transparent

That were the goals for QNX4 :slight_smile:

Regards

Armin

I have not seen this anywhere in docs or on the web.

Anyone know what it stands for?

\

  • GF

    \

I think the post more then answered the question, unlike your post, which
added nothing.


“Joan Baucells” <“Joan Baucells”@NoSpam.es> wrote in message
news:40C45347.D8286DB6@NoSpam.es

Is this a publicitary ng, or a technical one?

“Lawrence R. Sweet” wrote:

A unique feature of the QNX realtime operating system, FLEET creates a
single homogeneous set of resources that you can access transparently,
anywhere throughout the network. FLEET is an ultralight, high-speed
networking protocol. Its innovative and feature-rich design turns
network-connected machines into a single logical supercomputer. Because
FLEET is built on the message-passing architecture of the QNX OS, it
offers
the ultimate in flexibility. FLEET delivers:

a… Fault-tolerant networking
b… Load-balancing on the fly
c… Efficient performance
d… Extensible architecture
e… Transparent distributed processing

Fault-tolerant networking
If a cable or network card in one network fails, FLEET automatically
re-routes data through another network. This happens on the fly, without
involving application software, giving you automatic network
fault-tolerance.

Load-balancing on the fly
Network throughput is normally limited by the speed of your computer and
network hardware. With FLEET, data can be transmitted over multiple
networks
simultaneously, allowing you to double, triple, or even quadruple your
network bandwidth and throughput by placing multiple network cards in
each
computer and connecting them with separate cables. You can even mix
different types of network cards (e.g. Ethernet, FDDI) in the same
machine.

Efficient performance
FLEET network drivers are built to make the most of your networking
hardware. For example, when sending large blocks of data over an
Ethernet
network from one process to another, you get impressive throughput:

Network No. of client processes Throughput
10 Mbit Ethernet 1 1.1 Mbytes/sec
100 Mbit Ethernet 1 7.5 Mbytes/sec
(limited by network card)

Extensible architecture
Thanks to FLEET, a QNX network gives you unsurpassed flexibility.
Networking
processes are architecturally distinct from the OS, allowing you to
start
and stop a networked node at any time. This means you can add nodes to
your
network or remove them dynamically without reconfiguring your system.
And,
thanks to automatic network bridging, you can add different physical
networks to your LAN as well.

Transparent distributed processing
FLEET’s networking processes are deeply integrated into the heart of
message-passing and process-management primitives, making local and
network-wide IPC one and the same. Since IPC is network transparent, a
network of individual PCs appears as a single, seamless supercomputer.
The
end result? You never need to modify your applications to communicate
across
the network.

“Gordon Freeman” <> gfreeman@bigfoot.com> > wrote in message
news:c9nljm$mnm$> 1@inn.qnx.com> …
Is QNX native networking, “FLEET”, an acronym?

I have not seen this anywhere in docs or on the web.

Anyone know what it stands for?

\

  • GF

???

I apologize if I’ve offended someone. There wasn’t my intention.

Eric Norton wrote:

I think the post more then answered the question, unlike your post, which
added nothing.

“Joan Baucells” <“Joan Baucells”@NoSpam.es> wrote in message
news:> 40C45347.D8286DB6@NoSpam.es> …
Is this a publicitary ng, or a technical one?

“Lawrence R. Sweet” wrote:

A unique feature of the QNX realtime operating system, FLEET creates a
single homogeneous set of resources that you can access transparently,
anywhere throughout the network. FLEET is an ultralight, high-speed
networking protocol. Its innovative and feature-rich design turns
network-connected machines into a single logical supercomputer. Because
FLEET is built on the message-passing architecture of the QNX OS, it
offers
the ultimate in flexibility. FLEET delivers:

a… Fault-tolerant networking
b… Load-balancing on the fly
c… Efficient performance
d… Extensible architecture
e… Transparent distributed processing

Fault-tolerant networking
If a cable or network card in one network fails, FLEET automatically
re-routes data through another network. This happens on the fly, without
involving application software, giving you automatic network
fault-tolerance.

Load-balancing on the fly
Network throughput is normally limited by the speed of your computer and
network hardware. With FLEET, data can be transmitted over multiple
networks
simultaneously, allowing you to double, triple, or even quadruple your
network bandwidth and throughput by placing multiple network cards in
each
computer and connecting them with separate cables. You can even mix
different types of network cards (e.g. Ethernet, FDDI) in the same
machine.

Efficient performance
FLEET network drivers are built to make the most of your networking
hardware. For example, when sending large blocks of data over an
Ethernet
network from one process to another, you get impressive throughput:

Network No. of client processes Throughput
10 Mbit Ethernet 1 1.1 Mbytes/sec
100 Mbit Ethernet 1 7.5 Mbytes/sec
(limited by network card)

Extensible architecture
Thanks to FLEET, a QNX network gives you unsurpassed flexibility.
Networking
processes are architecturally distinct from the OS, allowing you to
start
and stop a networked node at any time. This means you can add nodes to
your
network or remove them dynamically without reconfiguring your system.
And,
thanks to automatic network bridging, you can add different physical
networks to your LAN as well.

Transparent distributed processing
FLEET’s networking processes are deeply integrated into the heart of
message-passing and process-management primitives, making local and
network-wide IPC one and the same. Since IPC is network transparent, a
network of individual PCs appears as a single, seamless supercomputer.
The
end result? You never need to modify your applications to communicate
across
the network.

“Gordon Freeman” <> gfreeman@bigfoot.com> > wrote in message
news:c9nljm$mnm$> 1@inn.qnx.com> …
Is QNX native networking, “FLEET”, an acronym?

I have not seen this anywhere in docs or on the web.

Anyone know what it stands for?

\

  • GF

Fault tolerant
Load balancing
Efficient
Extensive
Transparent

(if I remember well)

“Milan Pavicevic” <milan@pavicevic.com> wrote in message
news:ckug8e$3f8$1@inn.qnx.com

Fault tolerant
Load balancing
Efficient
Extensive
Transparent

+= Highly System Dependant and Non Portable :slight_smile:

// wbr

Ian Zagorskih <ianzag@megasignal.com> wrote:

“Milan Pavicevic” <> milan@pavicevic.com> > wrote in message
news:ckug8e$3f8$> 1@inn.qnx.com> …
Fault tolerant
Load balancing
Efficient
Extensive
Transparent

+= Highly System Dependant and Non Portable > :slight_smile:

Well, yeah. It is native networking.

If you want inter-operability, use TCP/IP.

-David

QNX Training Services
http://www.qnx.com/services/training/
Please followup in this newsgroup if you have further questions.