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 0 of 5] Add credit2 scheduler (EXPERIMENTAL)

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 0 of 5] Add credit2 scheduler (EXPERIMENTAL)
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Wed, 14 Apr 2010 08:59:28 -0700 (PDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Apr 2010 09:03:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7EB954E.FE28%keir.fraser@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4BC5D165.4010700@xxxxxxxxxxxxx C7EB954E.FE28%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks.  Unfortunately, after updating both hypervisor
and tools to cs21173 (from staging), xend seems to start fine, but
attempting to launch a domain yields:  

Xend has probably crashed!  Invalid or missing HTTP status code.

An immediate "xm list" shows that xend has not crashed
(or perhaps silently and successfully restarted), but
re-attempting to launch a domain yields the same message.

(George, no need to point out that this is probably
unrelated to the credit2 scheduler... but that would
imply that xen-unstable-not-staging is also broken.)

Keir, if staging passes your regression tests successfully
without the problem I am seeing, please let me know.
(And I'll try rolling back to 4.0 for now.)

> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Wednesday, April 14, 2010 8:53 AM
> To: George Dunlap; Dan Magenheimer
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [PATCH 0 of 5] Add credit2 scheduler
> (EXPERIMENTAL)
> 
> The patches are already available from the staging tree. They will get
> automatically pushed to the main tree when they pass the regression
> tests.
> 
>  K.
> 
> 
> On 14/04/2010 15:29, "George Dunlap" <george.dunlap@xxxxxxxxxxxxx>
> wrote:
> 
> > Keir has checked the patches in, so if you wait a bit, they should
> show
> > up on the public repository.
> >
> > The tool patch is only necessary for adjusting the weight; if you're
> OK
> > using the default weight, just adding "sched=credit2" on the xen
> > command-line should be fine.
> >
> > Don't forget that this isn't meant to perform well on multiple
> sockets
> > yet. :-)
> >
> >  -George
> >
> > Dan Magenheimer wrote:
> >> Hi George --
> >>
> >> I'm seeing some problems applying the patches (such as "malformed
> >> patch").  If you could send me a monolithic patch in an attachment
> >> and tell me what cset in http://xenbits.xensource.com/xen-
> unstable.hg
> >> that it successfully applies against, I will try to give my
> >> workload a test against it to see if it has the same
> >> symptoms.
> >>
> >> Also, do I need to apply the tools patch if I don't intend
> >> to specify any parameters, or is the xen patch + "sched=credit2"
> >> in a boot param sufficient?
> >>
> >> Thanks,
> >> Dan
> >>
> >>
> >>> -----Original Message-----
> >>> From: George Dunlap [mailto:george.dunlap@xxxxxxxxxxxxx]
> >>> Sent: Wednesday, April 14, 2010 4:26 AM
> >>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> >>> Cc: george.dunlap@xxxxxxxxxxxxx
> >>> Subject: [Xen-devel] [PATCH 0 of 5] Add credit2 scheduler
> >>> (EXPERIMENTAL)
> >>>
> >>> This patch series introduces the credit2 scheduler.  The first two
> >>> patches
> >>> introduce changes necessary to allow the credit2 shared runqueue
> >>> functionality
> >>> to work properly; the last two implement the functionality itself.
> >>>
> >>> The scheduler is still in the experimental phase.  There's lots of
> >>> opportunity to contribute with independent lines of development;
> email
> >>> George Dunlap <george.dunlap@xxxxxxxxxxxxx> or check out the wiki
> page
> >>> http://wiki.xensource.com/xenwiki/Credit2_Scheduler_Development for
> >>> ideas
> >>> and status updates.
> >>>
> >>> 19 files changed, 1453 insertions(+), 21 deletions(-)
> >>> tools/libxc/Makefile                      |    1
> >>> tools/libxc/xc_csched2.c                  |   50 +
> >>> tools/libxc/xenctrl.h                     |    8
> >>> tools/python/xen/lowlevel/xc/xc.c         |   58 +
> >>> tools/python/xen/xend/XendAPI.py          |    3
> >>> tools/python/xen/xend/XendDomain.py       |   54 +
> >>> tools/python/xen/xend/XendDomainInfo.py   |    4
> >>> tools/python/xen/xend/XendNode.py         |    4
> >>> tools/python/xen/xend/XendVMMetrics.py    |    1
> >>> tools/python/xen/xend/server/SrvDomain.py |   14
> >>> tools/python/xen/xm/main.py               |   82 ++
> >>> xen/arch/ia64/vmx/vmmu.c                  |    6
> >>> xen/common/Makefile                       |    1
> >>> xen/common/sched_credit.c                 |    8
> >>> xen/common/sched_credit2.c                | 1125
> >>> +++++++++++++++++++++++++++++
> >>> xen/common/schedule.c                     |   22
> >>> xen/include/public/domctl.h               |    4
> >>> xen/include/public/trace.h                |    1
> >>> xen/include/xen/sched-if.h                |   28
> >>>
> >>> _______________________________________________
> >>> Xen-devel mailing list
> >>> Xen-devel@xxxxxxxxxxxxxxxxxxx
> >>> http://lists.xensource.com/xen-devel
> >>>
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> 
> 

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

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