All of lore.kernel.org
 help / color / mirror / Atom feed
From: NISHIGUCHI Naoki <nisiguti@jp.fujitsu.com>
To: George Dunlap <dunlapg@umich.edu>, "Su, Disheng" <disheng.su@intel.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [RFC] Add static priority into credit scheduler
Date: Fri, 27 Mar 2009 11:39:38 +0900	[thread overview]
Message-ID: <49CC3C6A.6050308@jp.fujitsu.com> (raw)
In-Reply-To: <de76405a0903250335r3b2dbb5at589d2a999f118b5a@mail.gmail.com>

Hi Disheng and George,

Disheng, I'm glad to see your work.

George Dunlap wrote:
> I'd be interested to hear others' opinions.

I think that static priority is useful under some conditions.
But, as George said, I also think it is harder to configure properly.
And I'm anxious that it makes credits on non-RT vcpu meaningless.

I tested your patch in following environment.

   CPU: Intel Core2 Quad Q9450
   Chipset: Intel 82Q35
   VM: dom0 (4 vcpus), HVM (4 vcpus)
   Xen: c/s 19426
   HVM:
     RT priority (1)
     pass-through devcies
       PCI graphic board
       Integrated devices(audio, USB controller)
     playing video

With this configuration, HVM does not work well.
When HVM does not have RT priority, HVM works well.

I think we would need to consider the relationship between static 
priority and credit, handling of dom0 and driver domain, and so on.

Best regards,
Naoki Nishiguchi

  reply	other threads:[~2009-03-27  2:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20  9:18 [RFC] Add static priority into credit scheduler Su, Disheng
2009-03-20 12:42 ` George Dunlap
2009-03-23  7:33   ` Su, Disheng
2009-03-25 10:35     ` George Dunlap
2009-03-27  2:39       ` NISHIGUCHI Naoki [this message]
2009-03-27  3:29         ` Su, Disheng
2009-03-27  7:03           ` NISHIGUCHI Naoki
2009-03-27  8:05             ` Su, Disheng
2009-03-27 10:13               ` NISHIGUCHI Naoki
2009-03-27  4:29       ` Su, Disheng

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=49CC3C6A.6050308@jp.fujitsu.com \
    --to=nisiguti@jp.fujitsu.com \
    --cc=disheng.su@intel.com \
    --cc=dunlapg@umich.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.