Hi,
I want to improve transfer time between several machines in the same LAN
via manipulate Ethernet frame directly,because neither the Qnet Msg passing
nor TCP/IP stack speeds can’t statify our communication
requirements(transfer a size of 60Bytes package to 12 client machines in
every control cycle–1ms).On the other hand,it can improve transfer time via
multicast of Ethernet specification .
Do you think my idea feasibly???
Now I have got the technical specification of my NIC card,doesn’t I need
to stop the original driver of the NIC(3COM 905B-TX-NM) and then run my
portable ‘driver’ (I propose to write some codes to manipulate the NIC ) ??
And thanks for any idea of improving transfer time under QNX 6.20 PE in
advance.
Best regards!
\
Hichun Chen
Institute of Plasama Physics of Chinese Academy.
http://hichun.nease.net
hcchen@ipp.ac.cn
“Hichun Chen” <hcchen@mail.ipp.ac.cn> wrote in message
news:b8thkn$iud$1@inn.qnx.com…
Hi,
I want to improve transfer time between several machines in the same
LAN
via manipulate Ethernet frame directly,because neither the Qnet Msg
passing
nor TCP/IP stack speeds can’t statify our communication
requirements(transfer a size of 60Bytes package to 12 client machines in
every control cycle–1ms).On the other hand,it can improve transfer time
via
multicast of Ethernet specification .
You can use UDP and broadcast/multicast.
Do you think my idea feasibly???
Now I have got the technical specification of my NIC card,doesn’t I
need
to stop the original driver of the NIC(3COM 905B-TX-NM) and then run my
portable ‘driver’ (I propose to write some codes to manipulate the NIC )
??
You could also write your own protocol stack. Doing so you wouldn’t have to
deal with the hardware directlry which should REALLY be avoided.
And thanks for any idea of improving transfer time under QNX 6.20 PE
in
advance.
Best regards!
\
Hichun Chen
Institute of Plasama Physics of Chinese Academy.
http://hichun.nease.net
hcchen@ipp.ac.cn
Or you could write a filter between ip and ethernet and capture all the
packets coming up and manipulate them.That way you can work with various
NICs without any problem.
Sreekanth
“Mario Charest” postmaster@127.0.0.1 wrote in message
news:b8tlvn$n8b$1@inn.qnx.com…
“Hichun Chen” <> hcchen@mail.ipp.ac.cn> > wrote in message
news:b8thkn$iud$> 1@inn.qnx.com> …
Hi,
I want to improve transfer time between several machines in the same
LAN
via manipulate Ethernet frame directly,because neither the Qnet Msg
passing
nor TCP/IP stack speeds can’t statify our communication
requirements(transfer a size of 60Bytes package to 12 client machines in
every control cycle–1ms).On the other hand,it can improve transfer time
via
multicast of Ethernet specification .
You can use UDP and broadcast/multicast.
Do you think my idea feasibly???
Now I have got the technical specification of my NIC card,doesn’t I
need
to stop the original driver of the NIC(3COM 905B-TX-NM) and then run my
portable ‘driver’ (I propose to write some codes to manipulate the NIC )
??
You could also write your own protocol stack. Doing so you wouldn’t have
to
deal with the hardware directlry which should REALLY be avoided.
And thanks for any idea of improving transfer time under QNX 6.20 PE
in
advance.
Best regards!
\
Hichun Chen
Institute of Plasama Physics of Chinese Academy.
http://hichun.nease.net
hcchen@ipp.ac.cn
\
–
Hichun Chen
Institute of Plasama Physics of Chinese Academy.
Hi,
I want to improve transfer time between several machines in the same
LAN
via manipulate Ethernet frame directly,because neither the Qnet Msg
passing
nor TCP/IP stack speeds can’t statify our communication
requirements(transfer a size of 60Bytes package to 12 client machines in
every control cycle–1ms).On the other hand,it can improve transfer time
via
multicast of Ethernet specification .
You can use UDP and broadcast/multicast.
^^^^^But each client has some data send to the server in every control
cycle(1ms),the round trip time might exceed 1ms.
Do you think my idea feasibly???
Now I have got the technical specification of my NIC card,doesn’t I
need
to stop the original driver of the NIC(3COM 905B-TX-NM) and then run my
portable ‘driver’ (I propose to write some codes to manipulate the NIC )
??
You could also write your own protocol stack. Doing so you wouldn’t have
to
deal with the hardware directlry which should REALLY be avoided.
In communication model the protocol processing induce the most delay. On the
other hand,write a special light driver under QNX Neutrino is easy (QSSL’s
doc said) 