We have to buffer data from guest as ports may not consume all the data
in one go or the guest could be fast in sending data and the apps may
not consume at the same rate.
We keep caching data the guest sends us till a port accepts it. However,
this could lead to an OOM condition where a rogue
Anthony Liguori anth...@codemonkey.ws writes:
On 01/12/2010 01:16 AM, Amit Shah wrote:
BTW I don't really want this too, I can get rid of it if everyone agrees
we won't support clipboard writes 4k over vnc or if there's a better
idea.
Why bother trying to preserve message boundaries?
On 01/13/2010 11:14 AM, Markus Armbruster wrote:
Anthony Liguorianth...@codemonkey.ws writes:
On 01/12/2010 01:16 AM, Amit Shah wrote:
BTW I don't really want this too, I can get rid of it if everyone agrees
we won't support clipboard writes 4k over vnc or if there's a better
On 01/12/2010 01:16 AM, Amit Shah wrote:
BTW I don't really want this too, I can get rid of it if everyone agrees
we won't support clipboard writes 4k over vnc or if there's a better
idea.
Why bother trying to preserve message boundaries? I think that's the
fundamental question.
On (Tue) Jan 12 2010 [09:00:52], Anthony Liguori wrote:
On 01/12/2010 01:16 AM, Amit Shah wrote:
BTW I don't really want this too, I can get rid of it if everyone agrees
we won't support clipboard writes 4k over vnc or if there's a better
idea.
Why bother trying to preserve message
On 01/12/2010 09:13 AM, Amit Shah wrote:
On (Tue) Jan 12 2010 [09:00:52], Anthony Liguori wrote:
On 01/12/2010 01:16 AM, Amit Shah wrote:
BTW I don't really want this too, I can get rid of it if everyone agrees
we won't support clipboard writes 4k over vnc or if there's a better
On (Tue) Jan 12 2010 [09:46:55], Anthony Liguori wrote:
On 01/12/2010 09:13 AM, Amit Shah wrote:
On (Tue) Jan 12 2010 [09:00:52], Anthony Liguori wrote:
On 01/12/2010 01:16 AM, Amit Shah wrote:
BTW I don't really want this too, I can get rid of it if everyone agrees
we won't
On 01/12/2010 09:49 AM, Amit Shah wrote:
On (Tue) Jan 12 2010 [09:46:55], Anthony Liguori wrote:
On 01/12/2010 09:13 AM, Amit Shah wrote:
On (Tue) Jan 12 2010 [09:00:52], Anthony Liguori wrote:
On 01/12/2010 01:16 AM, Amit Shah wrote:
BTW I don't really want
On (Tue) Jan 12 2010 [09:55:41], Anthony Liguori wrote:
On 01/12/2010 09:49 AM, Amit Shah wrote:
On (Tue) Jan 12 2010 [09:46:55], Anthony Liguori wrote:
On 01/12/2010 09:13 AM, Amit Shah wrote:
On (Tue) Jan 12 2010 [09:00:52], Anthony Liguori wrote:
On 01/12/2010 01:16
On (Fri) Jan 08 2010 [13:35:03], Jamie Lokier wrote:
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.
For vnc putting stuff from a guest clipboard into vnc client clipboard
using
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
Amit Shah wrote:
On (Fri) Jan 08 2010 [13:35:03], Jamie Lokier wrote:
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.
For vnc putting stuff from a guest clipboard into vnc
On (Mon) Jan 11 2010 [10:45:53], Jamie Lokier wrote:
Amit Shah wrote:
On (Fri) Jan 08 2010 [13:35:03], Jamie Lokier wrote:
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.
Amit Shah wrote:
Are you talking about a VNC protocol command between qemu's VNC server
and the user's VNC client, or a private protocol between the guest and
qemu's VNC server?
What happens is:
1. Guest puts something on its clipboard
2. An agent on the guest gets notified of new
On 01/11/2010 05:33 PM, Jamie Lokier wrote:
Amit Shah wrote:
Are you talking about a VNC protocol command between qemu's VNC server
and the user's VNC client, or a private protocol between the guest and
qemu's VNC server?
What happens is:
1. Guest puts something on its clipboard
On 01/11/2010 02:39 AM, Amit Shah wrote:
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
On (Mon) Jan 11 2010 [18:28:52], Anthony Liguori wrote:
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
On (Mon) Jan 11 2010 [23:33:56], Jamie Lokier wrote:
Amit Shah wrote:
Are you talking about a VNC protocol command between qemu's VNC server
and the user's VNC client, or a private protocol between the guest and
qemu's VNC server?
What happens is:
1. Guest puts something on its
Amit Shah wrote:
On (Fri) Jan 08 2010 [01:12:31], Jamie Lokier wrote:
Amit Shah wrote:
Guests send us one buffer at a time. Current guests send buffers sized
4K bytes. If guest userspace applications sent out 4K bytes in one
write() syscall, the write request actually sends out
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
Amit Shah wrote:
Guests send us one buffer at a time. Current guests send buffers sized
4K bytes. If guest userspace applications sent out 4K bytes in one
write() syscall, the write request actually sends out multiple buffers,
each of 4K in size.
This usually isn't a problem but for some
On (Fri) Jan 08 2010 [01:12:31], Jamie Lokier wrote:
Amit Shah wrote:
Guests send us one buffer at a time. Current guests send buffers sized
4K bytes. If guest userspace applications sent out 4K bytes in one
write() syscall, the write request actually sends out multiple buffers,
each of
Guests send us one buffer at a time. Current guests send buffers sized
4K bytes. If guest userspace applications sent out 4K bytes in one
write() syscall, the write request actually sends out multiple buffers,
each of 4K in size.
This usually isn't a problem but for some apps, like VNC, the
Guests send us one buffer at a time. Current guests send buffers sized
4K bytes. If guest userspace applications sent out 4K bytes in one
write() syscall, the write request actually sends out multiple buffers,
each of 4K in size.
This usually isn't a problem but for some apps, like VNC, the
Guests send us one buffer at a time. Current guests send buffers sized
4K bytes. If guest userspace applications sent out 4K bytes in one
write() syscall, the write request actually sends out multiple buffers,
each of 4K in size.
This usually isn't a problem but for some apps, like VNC, the
On 12/23/2009 01:52 PM, Amit Shah wrote:
Guests send us one buffer at a time. Current guests send buffers sized
4K bytes. If guest userspace applications sent out 4K bytes in one
write() syscall, the write request actually sends out multiple buffers,
each of 4K in size.
This usually isn't a
26 matches
Mail list logo
