From mboxrd@z Thu Jan 1 00:00:00 1970 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: Your message of "Thu, 29 Apr 2010 11:34:44 EDT." <046b9c874815d108c6ffb7a857e847a7@kw.quanstro.net> References: <5fa9fbfe115a9cd5a81d0feefe413192@quintile.net> <4fa1305e0f56a0ef89c2e05320fa5997@coraid.com> <40cf59cfc2735e232f0fd67df725e65d@kw.quanstro.net> <046b9c874815d108c6ffb7a857e847a7@kw.quanstro.net> From: Bakul Shah Date: Thu, 29 Apr 2010 10:08:59 -0700 Message-Id: <20100429170859.2EBE05B78@mail.bitblocks.com> Subject: Re: [9fans] A simple experiment Topicbox-Message-UUID: 12c78be8-ead6-11e9-9d60-3106f5b1d025 On Thu, 29 Apr 2010 11:34:44 EDT erik quanstrom wrote: > > Wasn't IL somewhat abandoned because to make it as good as TCP you > > basically had to implement TCP anyway? > > due to a failure of vision, the internet only does > well with certain types of ip packets. :-) > il is still an excellent protocol for local networks. > > > 9P doesn't require any flow control? That doesn't seem right :-) But then > > 9p, like aoe, is a ping-pong protocol. each message requires an ack. > therefore, the transport layer doesn't need flow control. Therefore, it is also not able to utilise bandwidth effectively over longhaul links. As an example, US coast to coast round trip time latency is about 100ms. Now consider fcp. Each worker thread of fcp does 8K read/writes. Due to pingponging, the *most* a thread can xfer coast to coast is 80KBps (for 16 threads, 1.28MBps). It is actually much worse since each thread doesn't even overlap reads with writes. Short of a sliding window that is as large as the capacity of the pipe, you can't expect to keep it full. As usual one has to trade off simplicity vs performance. I do hope 9p evolves.