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] [PATCH] XML-RPC: Cope with large integers on x86-64 syst

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] XML-RPC: Cope with large integers on x86-64 systems
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Tue, 28 Mar 2006 09:18:24 -0600
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>
Delivery-date: Tue, 28 Mar 2006 15:19:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9bf498105410d761383ca3185d5f7369@xxxxxxxxxxxx>
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>
References: <44289F79.9000501@xxxxxxxxxx> <9bf498105410d761383ca3185d5f7369@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mail/News 1.5 (X11/20060309)
Keir Fraser wrote:

On 28 Mar 2006, at 03:29, Anthony Liguori wrote:

Attached patch fixes a problem in marshaling large integers. It seems to only occur on systems with very large memory. However, on those systems, it's a show-stopper. I see this as a temporary solution until we can sanitize the XML-RPC functions and get rid of all the S-Expression stuff.

I thought the main reason to push the XML-RPC stuff before 3.0.2 was to give a measure of stability to that interface, and provide a more supportable interface for vendors to lock onto? That reasoning doesn't really hold if the core of the interface needs more refactoring and cleaning up post 3.0.2.

The approach for the XML-RPC work was to first get XML-RPC support into the tree and then build a standard interface. Building a standard interface requires refactoring (which will be simplification) to get rid of things like S-Expression configs. To get rid of that, we have to get rid of the S-Expression/HTTP layer.

This whole reasoning is outlined on the wiki page.

http://wiki.xensource.com/xenwiki/Xend/XML-RPC

Regards,

Anthony Liguori

 -- Keir



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