I have 3 machines with two 6.2.1 and one 6.3.2.
Under /net, and two 6.2.1 machines can see each other, while 6.3.2 can only see itself. All of them are in a switch network and can surf the web. What’s the problem here?
THX!
That’s right. The Qnet in QNX 6.3 and above is not compatible with the Qnet from 6.2.1 and below. There is, however, a compatible qnet in 6.3 (see npm-qnet-compat.so in the docs).
Thx. i configured 6.3.2 to use npm-qnet-compat.so and all of them can see one another now. And it seems that qnx is going to discard this manager in the future release. I want to know if there is any performance difference between the two qnet methods.
Thx. i configured 6.3.2 to use npm-qnet-compat.so and all of them can see one another now. And it seems that qnx is going to discard this manager in the future release. I want to know if there is any performance difference between the two qnet methods.
Well, it depends whether you consider “working” to be a component of “performance” if so, then the new qnet performs 100% better than the old qnet
rgallen, you say that like the old version did not work at all. Was there something specific that you know of that didn’t work?
The old qnet was not reliable. The new one is very reliable.
I also have seen the old QNET to be problematic. In some cases it worked great, e.g. I could redirect an audio stream to a /dev/snd an another node by creating a /net link. But in other cases it just would fail, the connection would die or it would be very slow.
The new QNET is much more stable, actually I never saw it failing (except for a network driver problem, but that’s not QNET’s fault). And it is much faster aswell, I did some performance tests.
The question generally is what you want to achieve. For QNET though, I would recommend to use the new one in any case g.