Re: [Etherboot-developers] Re: TCP and HTTP support

[<ke...@et...>]

>> if you patch against 5.3.0 (5.1.10 is close enough) and remove all the
>> large buffers from the stack
>
>I had been wondering how to do that best. I don't really need much 
>space. The only large structures are the ones that hold the current HTTP 
>header/state (about 100 bytes), any URL found in redirects (80 bytes), 
>and the buffer used for assembling outgoing packets (1500 bytes). The 
>latter is the problem. I know that none of my packets are large, so I 
>guess I could just shrink this buffer (576 would make a lot of sense), 
>and impose a maximum segment size for outgoing TCP packets. Would that 
>be acceptable?
>
>Alternatively, I could allocate the buffer in the BSS.
>
>What is the prefered solution?

Put large objects in the BSS, there's no ROM space penalty for that and
I'm less concerned about footprint now that Etherboot runs relocated.  I
don't mind a full size packet buffer. The size should be configurable as
I suspect somebody called Eric may want to use Etherboot across media
with larger frame sizes someday. :-)

What I think will be interesting is learning how well it plays with
server TCP stacks, whether breaking off a boot will leave dangling
connections which have to timeout, and that sort of thing. And of
course, if 50 clients all boot at once, the web server will think it's
under attack. Anyway Jim's mob will do this testing for us. :-)