All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Ackaouy <ack@xensource.com>
To: Atsushi SAKAI <sakaia@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Q] about Credit Scheduler Dom0 Scheduling policy.
Date: Tue, 24 Oct 2006 10:49:52 +0100	[thread overview]
Message-ID: <20061024094952.GA29248@cockermouth.uk.xensource.com> (raw)
In-Reply-To: <200610240647.k9O6lYQR004608@fjmscan503.ms.jp.fujitsu.com>

On Tue, Oct 24, 2006 at 03:46:59PM +0900, Atsushi SAKAI wrote:
> Currently, I am testing on IA64.
> CPU=1595MHz
> itc=1595MHz

In the chunk of the trace file you sent, the scheduler is
behaving quite well. The domU being woken up at various
times on a clock boundary (10ms) must be due to some
timers.

There is one case where dom0 wakes up and doesn't preempt
the CPU (the first dom0 wake in the trace file) though. I
would like to see a bigger chunk of your trace file and
scan it to see if there are other examples of this.

If it's too big for the list, can you send it to me
privately or put it up on some publicly accessible server
somewhere?

Thanks.

  reply	other threads:[~2006-10-24  9:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 11:49 [Q] about Credit Scheduler Dom0 Scheduling policy Atsushi SAKAI
2006-10-18 13:11 ` Emmanuel Ackaouy
2006-10-18 13:24   ` Emmanuel Ackaouy
2006-10-23  4:13     ` Atsushi SAKAI
2006-10-23 14:32       ` Emmanuel Ackaouy
2006-10-24  6:46         ` Atsushi SAKAI
2006-10-24  9:49           ` Emmanuel Ackaouy [this message]
2006-10-25 10:29           ` Emmanuel Ackaouy
2006-10-25 13:02             ` Atsushi SAKAI
2006-10-25 14:03               ` Emmanuel Ackaouy
2006-10-26  6:15                 ` Atsushi SAKAI
2006-10-26  8:35                   ` Atsushi SAKAI
2006-10-26  8:42                     ` Emmanuel Ackaouy
2006-10-26 12:52                       ` Pasi Kärkkäinen
2006-10-26 13:04                         ` Emmanuel Ackaouy
2006-10-26 13:47                           ` Pasi Kärkkäinen

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=20061024094952.GA29248@cockermouth.uk.xensource.com \
    --to=ack@xensource.com \
    --cc=sakaia@jp.fujitsu.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 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.