Re: [Qemu-devel] [PATCH 5/8] virtio-serial-bus: Add support for buffering guest output, throttling guests

[Amit Shah <amit.shah@redhat.com>]

On (Fri) Jan 08 2010 [10:26:59], Anthony Liguori wrote:
> On 01/08/2010 07:35 AM, Jamie Lokier wrote:
>> Sometimes it looks like TCP is maintaining write boundaries, but it is
>> just an artifact of its behaviour on many systems, and is not reliable
>> even on those systems where it seems to happen most of the time.  Even
>> when connecting to localhost, you cannot rely on that.  I have seen
>> people write code assuming TCP keeps boundaries, and then some weeks
>> later they are very confused debugging their code because it is not
>> reliable...
>>
>> Since VNC is clearly designed to work over TCP, and is written by
>> people who know this, I'm wondering why you think it needs to be
>> different for virtio-serial.
>>    
>
> I'm confused about why the buffering is needed in the first place.
>
> I would think that any buffering should be pushed back to the guest.   
> IOW, if there's available data from the char driver, but the guest  
> doesn't have a buffer.  Don't select on the char driver until the guest  
> has a buffer available.  If the guest attempts to write data but the  
> char driver isn't ready to receive data, don't complete the request  
> until the char driver can accept data.

This is a different thing from what Jamie's talking about. A guest or a
host might be interested in communicating data without waiting for the
other end to come up. The other end can just start consuming the data
(even the data that it missed while it wasn't connected) once it's up.

(I can remove this option for now and add it later, if you prefer it
that way.)

		Amit