That's promising. I'm looking forward to trying it out. I ran into one tiny snag though.
We use three different images for chain loading depending on the hardware. We use undionly.kpxe, undionly.kkpxe, and r8169.kpxe. I successfully built the first two but I'm getting an "undefined symbol" error when attempting to build r8169. The actual card says it is an rtl8167. I'm curious what is the correct kpxe file to build and more importantly, how would I know that without bothering you guys the next time? I noticed there are several possible builds I can do (rtl8139, rtl8180, rtl8185); do any of these supersede r8169? Matt Error when building r8169.kpxe: src$ make ./bin/r8169.kpxe [LD] bin/r8169.kpxe.tmp arch/i386/scripts/i386.lds:1: undefined symbol `obj_r8169' referenced in expression make: *** [bin/r8169.kpxe.tmp] Error 1 On Thu, Aug 2, 2012 at 6:32 PM, Michael Brown <[email protected]>wrote: > On Thursday 02 Aug 2012 23:06:55 Hoey, Matthew wrote: > > Here is an example script that we run. Very simple, but we have problems > > over high latency lines (160ms). The window didn't seem to get larger > than > > 5192. It takes about 7 mins to download a 15MB file where as after I > > install CentOS and use wget it downloads in 1.5 secs. Is there a way to > > tell ipxe to scale the window size? > > Use a version of iPXE more recent than July 8 2012. Several TCP > performance > improvements went in recently, and iPXE now uses a default window size of > 256kB rather than 8kB. > > Michael >
_______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
