RE: [PATCH 0 of 5] Add credit2 scheduler (EXPERIMENTAL)

[Dan Magenheimer <dan.magenheimer@oracle.com>]

While someone is fixing up the new NUMA code, it would be
nice if the output of the NUMA info in "xm info" would
conform to the rest of the "xm info" output (e.g. all
on the same line, maybe "topology: cpu=X node=Y etc").
I often write scripts that parse various Xen output,
and I suspect many Xen-based products do also,
so format consistency is always good.

> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Sent: Wednesday, April 14, 2010 10:36 AM
> To: Dulloor
> Cc: George Dunlap; Dan Magenheimer; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] [PATCH 0 of 5] Add credit2 scheduler
> (EXPERIMENTAL)
> 
> On 14/04/2010 17:31, "Dulloor" <dulloor@gmail.com> wrote:
> 
> >> No, it crashes for me too. I think it's related to the recent NUMA
> patches.
> > Keir, which numa patches
> 
> Nitin's interface-changing patch, and the ensuing patch to remove
> sockets_per_node. Not that I'm certain, but it was around then that the
> crashes began, and that's what touched the Xc Python extension package
> (and
> C extensions to Python code are usually what make Python programs
> crash).
> 
>  -- Keir
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel