This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] unnecessary removal of guest console characters

To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] unnecessary removal of guest console characters
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 11 Apr 2008 16:46:48 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Fri, 11 Apr 2008 08:48:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080411151146.GN4717@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acib60Bkfu/MUAfeEd2rcQAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] unnecessary removal of guest console characters
User-agent: Microsoft-Entourage/
The 'application' in this case is the kernel. The data in this case is
console logs and possibly output from an interactive login. Responsiveness
of the former is critical, even, I would say, if that's at the expense of
integrity of the latter.

 -- Keir

On 11/4/08 16:11, "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx> wrote:

> Keir Fraser, le Fri 11 Apr 2008 16:03:57 +0100, a écrit :
>> Buffering happens in the daemon, not in the inter-domain ring. If we switch
>> to your strategy then overflow leads to the guest hanging rather than
>> characters being dropped.
> The guest itself doesn't hang, the application inside the guest that
> produces the output does hang, and that's what I would expect if I am
> not looking at it, rather than the risk of loosing data because of a
> non-end-to-end flow control.
> Samuel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>