The routing of CAN frames inside the kernel makes sense because of the missing 
copy to/from userspace and the scheduling that happens to userspace apps.
First tests proved a low latency (about 22 usecs on my Core2Duo 2GHz) and
especially a low jitter for the routed CAN frames.
  
Would like to try this out, but could you describe how you measured to get 22usec? What CAN hardware did you use, how many ports you have tested with would also be nice to know :)

I try to use a test like the following:
"Routing delay is measured from the last bit of an message on one port and the first bit of the of the same message on another port. Measured @ 1Mbps and the last frame of a 30 message back to back burst."
_______________________________________________
Socketcan-core mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-core


_______________________________________________
Socketcan-core mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-core

Reply via email to