From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dulloor <dulloor@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 5] Add credit2 scheduler (EXPERIMENTAL)
Date: Wed, 14 Apr 2010 17:36:06 +0100 [thread overview]
Message-ID: <C7EBAD86.113FB%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <t2s940bcfd21004140931h2037f1fbidd434af52f72b252@mail.gmail.com>
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
next prev parent reply other threads:[~2010-04-14 16:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 10:26 [PATCH 0 of 5] Add credit2 scheduler (EXPERIMENTAL) George Dunlap
2010-04-14 10:26 ` [PATCH 1 of 5] credit2: Add context_saved scheduler callback George Dunlap
2010-04-14 10:26 ` [PATCH 2 of 5] credit2: Flexible cpu-to-schedule-spinlock mappings George Dunlap
2010-04-14 10:26 ` [PATCH 3 of 5] credit2: Add a scheduler-specific schedule trace class George Dunlap
2010-04-14 10:26 ` [PATCH 4 of 5] credit2: Add credit2 scheduler to hypervisor George Dunlap
2010-04-14 10:26 ` [PATCH 5 of 5] credit2: Add toolstack options to control credit2 scheduler parameters George Dunlap
[not found] ` <7db7f696-1f0b-44d0-8f7b-eea1be5167dd@default>
2010-04-14 14:29 ` [PATCH 0 of 5] Add credit2 scheduler (EXPERIMENTAL) George Dunlap
2010-04-14 14:52 ` Keir Fraser
2010-04-14 15:59 ` Dan Magenheimer
2010-04-14 16:23 ` Keir Fraser
2010-04-14 16:31 ` Dulloor
2010-04-14 16:36 ` Keir Fraser [this message]
2010-04-14 17:04 ` Dan Magenheimer
2010-04-14 16:46 ` Dan Magenheimer
2010-04-15 20:11 ` Dan Magenheimer
[not found] ` <4BC664E1.7090304@purdue.edu>
2010-04-15 13:53 ` George Dunlap
2010-04-15 16:46 ` Naresh Rapolu
2010-04-15 17:33 ` Dulloor
2010-04-15 18:57 ` Naresh Rapolu
[not found] ` <h2x940bcfd21004140841kcdffe330xff5d749d43392fe3@mail.gmail.com>
2010-04-15 14:17 ` George Dunlap
2010-04-17 20:29 ` Dulloor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C7EBAD86.113FB%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=dulloor@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).