From: Lyscars, J. <jly...@en...> - 2008-09-12 19:30:44
|
Hello Al, With the rest of the test suite performing as expected, I moved onto the burst testing capabilities. With this test, everything appears to move along successfully until the test appears to hang after the size of 1450: Test # 16 TIPC blaster/blastee (SOCK_RDM) test...STARTED! Sent 100000 packets of size 1 in 4680 ms (100000 bit/s) Sent 100000 packets of size 32 in 4690 ms (5400000 bit/s) Sent 100000 packets of size 64 in 4730 ms (10800000 bit/s) Sent 100000 packets of size 100 in 4790 ms (16700000 bit/s) Sent 100000 packets of size 128 in 4850 ms (21100000 bit/s) Sent 100000 packets of size 256 in 4990 ms (41000000 bit/s) Sent 100000 packets of size 512 in 5250 ms (78000000 bit/s) Sent 100000 packets of size 1000 in 7530 ms (106200000 bit/s) Sent 100000 packets of size 1024 in 7610 ms (107600000 bit/s) Sent 100000 packets of size 1280 in 7990 ms (128100000 bit/s) Sent 100000 packets of size 1450 in 8240 ms (140700000 bit/s) Now looking at the code in tipc_ts_client.c int cblastSize[] = { 1, 32, 64, 100, 128, 256, 512, 1000, 1024, 1280, 1450, 2048, 8192, 10000, 0}; it appears that the next group of packets that should be sent are size 2048. Now, knowing that the MTU of my Ethernet bearer is 1500 bytes, is there any way for me to know if I am running into that limitation or not? Shouldn't I expect TIPC to fragment and reassemble beyond the bearer MTU size? I am currently testing with version 1.5.12. Thanks, John Lyscars jly...@en...<mailto:jly...@en...> |