Ethernet packets are range from 46-1500bytes, or there abouts, so
anything is being broken up. Well, anything over 1500 bytes.
I'll give the even multiples of 32768 a try and see how that goes.
(Well, there seems to be support for frame sizes up to 9000 bytes in
Gigabit Ethernet.)
I'm going to
I encourage people to answer their own questions!
This way you get the stars you deserve.
Your numbers look good.
Ben
Adding to my previous;
I have gotten good results using VI server technology and using call
by reference to get data.
I have never attempted to push the trasfer rates you are looking at
but I think it is worth a quick try.
The beauty of this approach (IMHO) is ZERO TCP DETAILS (sorry) to
code.
Hi Adam,
It has been a couple of days and no response on this Q so I will
relpy.
First, you have done your homework well. I have not used the TCP
functions from Sheldon Instruments so I can not comment on that.
I think the Naegel option would help if you were send alot of small
packets that
