summaryrefslogtreecommitdiffstats
path: root/src/core
diff options
context:
space:
mode:
authorMichael Brown2008-06-11 10:41:31 +0200
committerMichael Brown2008-06-11 10:41:31 +0200
commit5d36ec6721070e4efe817a853612837535019718 (patch)
tree2ec2a20ec3220457d202a399dcfee791db77f655 /src/core
parent[retry] Add start_timer_fixed() (diff)
downloadipxe-5d36ec6721070e4efe817a853612837535019718.tar.gz
ipxe-5d36ec6721070e4efe817a853612837535019718.tar.xz
ipxe-5d36ec6721070e4efe817a853612837535019718.zip
[slam] Implement SLAM flow control
On any fast network, or with any driver that may drop packets (e.g. Infiniband, which has very small RX rings), the traditional usage of the SLAM protocol will result in enormous numbers of packet drops and a consequent large number of retransmissions. By adapting the client behaviour, we can force the server to act more like a multicast TFTP server, with flow control provided by a single master client. This behaviour should interoperate with any traditional SLAM client (e.g. Etherboot 5.4) on the network. The SLAM protocol isn't actually documented anywhere, so it's hard to define either behaviour as compliant or otherwise.
Diffstat (limited to 'src/core')
0 files changed, 0 insertions, 0 deletions