Changes between Version 20 and Version 21 of Internal/DesignNotes
- Timestamp:
- Apr 10, 2006, 4:47:10 AM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/DesignNotes
v20 v21 25 25 [[Image(Internal/DesignNotes:num-pkts-recvd.3.png)]] 26 26 27 10000 packets were sent "as fast as possible". There was no "sleep" statement between two send events at the sender. The figures above show the number of packets lost per receiver (on the left) and the number of successful packet receptions (on the right). It is unclear from current experiments as to where this loss is occurring. Some sources of this loss could be27 10000 packets were sent "as fast as possible". There was no "sleep" statement between two consecutive send events at the sender. The figures above show the number of packets lost per receiver (on the left) and the number of successful packet receptions (on the right). It is unclear from current experiments as to where this loss is occurring. Some sources of this loss could be 28 28 * buffer (between user-space and kernel-space, between kernel and driver, between driver and card) overflows at the sender or receiver? 29 29 * the switches in the network cannot handle the load? Seems unlikely. … … 34 34 [[Image(Internal/DesignNotes:num-pkts-recvd.2.png)]] 35 35 36 5000 packets were sent "as fast as possible". There was no "sleep" statement between two send events at the sender. The figures above show the number of packets lost per receiver (on the left) and the number of successful packet receptions (on the right). It is unclear from current experiments as to where this loss is occurring.36 5000 packets were sent "as fast as possible". There was no "sleep" statement between two consecutive send events at the sender. The figures above show the number of packets lost per receiver (on the left) and the number of successful packet receptions (on the right). It is unclear from current experiments as to where this loss is occurring. 37 37 38 38 = Design Notes for nodehandler =