WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [RFC][PATCH] 1/3] [XEN] Use explicit bit sized fields fo

To: George Dunlap <dunlapg@xxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH] 1/3] [XEN] Use explicit bit sized fields for exported xentrace data.
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Thu, 30 Nov 2006 17:03:26 +0000
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 30 Nov 2006 09:03:35 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <de76405a0611300858x2fc39dd1rc01c2fc97cc31e4@xxxxxxxxxxxxxx>
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: AccUoXNMsgOsGoCUEdubHwAX8io7RQ==
Thread-topic: [Xen-devel] [RFC][PATCH] 1/3] [XEN] Use explicit bit sized fields for exported xentrace data.
User-agent: Microsoft-Entourage/11.2.5.060620


On 30/11/06 16:58, "George Dunlap" <dunlapg@xxxxxxxxx> wrote:

> Hmm... this has the unfortunate side-effect of doubling the size of
> the trace, and effectively halving the effectiveness of the trace
> buffer in avoiding drops.  My moderate-length traces are already in
> the gigabyte range, and I occasionally lose trace records even with a
> buffer size of 256.  It would be really nice if we could avoid that.
> 
> I happen to be using the VMENTER/VMEXIT tracing, which could be
> consolidated into one record if we went to a 64-bit trace.  Is anyone
> else doing high-bandwidth tracing that this would affect in a
> significantly negative way?

As we move increasingly towards x86/64 this is an issue that will need to be
addressed even if we leave the tracing fields as longs.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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