[U-Boot] [PATCH 1/1] efi_loader: add a README.iscsi describing booting via iSCSI

[Duncan Hare <dh@synoia.com>]

From: Heinrich Schuchardt <xypron.debian@gmx.de>
 To: Duncan Hare <dh@synoia.com>; Alexander Graf <agraf@suse.de> 
Subject: Re: [U-Boot] [PATCH 1/1] efi_loader: add a README.iscsi describing booting via iSCSI
  
On 01/25/2018 08:39 PM, Duncan Hare wrote:
>>> ----- Forwarded Message -----
>>>  From: Alexander Graf <agraf@suse.de>
>>>  To: Heinrich Schuchardt <xypron.glpk@gmx.de> 
>> 
>>>> The appended README explains how U-Boot and iPXE can be used
>>>> to boot a diskless system from an iSCSI SAN.
>>>>

>> We are implementing a limited TCP and a wget (http 1.0) app.>> It is almost ready for an test release. Selective Acknowledgment (SACK)
>> is under test as a final piece of the TCP stack.

In which git can I find the code?
>> 
>> We have noticed that omitting the http 1.0 declaration in
>> downloading the kernel from an nginx web server that we remove the
>> overhead of an http header completely.
>> 

> RFC 1945 - Hypertext Transfer Protocol -- HTTP/1.0

> You should not program to please another accommodating software but
> according to a standard.
I agree. The comment was a FYI.

> The key to TCP performance is supporting multiple packets in flight.
And we do. That's set in include/net.h in the buffer definitions.With single packet-at-a time one might as well stick with udp.
I've worked on network communication protocols since 1973.c programming, not so much. git, I'm a newb.



HeinrichIt is not yet pushed to git.I need to fix the bugs in SACK before taking that step. 
I had hoped this week but I was delayed by flu.
It adheres to http 1.0. It is a minimal implementation.
It is relatively fast. It drives a Raspberry Pi at 10 M bits/sec, 
the limitation being the raspberry pi processor speed.

I can send you a tarball, together with the changes to tftp.c for testing that a downloaded image is correct.

Regards Duncan Hare

714 931 7952