we use qnet bind to ether on a network with several ppc405 in an embedde
“Oliver” <email@example.com> schrieb im Newsbeitrag
We have a lot of problems with Qnet stability/performance. E.g.
- machines that are restarted are not discovered by other machines
that are still running. (Until I manually ‘ls’ into /net/machine_x)
same thing if the node is not touched for a longer time.
- depending on the topology (switches/hubs) the performance is extremly
poor. Copying 500 KB takes 10 sec on a 100MBit/s Lan!
we got about 2MByte/sec with filetransfer to another node via a switch on a
100MBit embedded Lan. But that is not enough with a theoretical data rate of
- Connections are lost while accessing a machine, e.g. copying a file
(Errors: “Host is down” and “Bad file descripter”)
similar but low frequency behaviour if large amounts of data are
transferred, also we got following errors in the slogger, which we could not
“Jan 02 00:50:32 7 15 0 npm-qnet(l3_uip): Bad packet length at
l3_uip.c:276 (Invalid argument)”
Does anyone have any similar problems? Or can Qnet be replaced by
something else, or at least Qnet’s ndp? Would HA help us with this in
may be with nfs or cifs for access to filesystems, but not to access other
resources of remote nodes.
We use QNX 6.2.1B.