All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yang, Xiaowei" <xiaowei.yang@intel.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] use atomic_t type for system wide credit scheduler statistics
Date: Mon, 09 Mar 2009 16:30:39 +0800	[thread overview]
Message-ID: <49B4D3AF.7050705@intel.com> (raw)
In-Reply-To: <C5DA7F2D.47D3%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> Not while csched stats are enabled by default. They get cranked all over the
> place. How much does this race matter? We probably just lose a few
> increments?

Yes. The higher frequency the count is updated, the more increments lost 
can we see - comparing to atomic version, counts like "vcpu_check" and 
"scheduele" lose increments very obviously due to race.

Thanks,
xiaowei

  reply	other threads:[~2009-03-09  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09  7:46 [PATCH] use atomic_t type for system wide credit scheduler statistics Yang, Xiaowei
2009-03-09  8:09 ` Keir Fraser
2009-03-09  8:30   ` Yang, Xiaowei [this message]
2009-03-09  8:36     ` Keir Fraser
2009-03-09 10:04       ` Yang, Xiaowei

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=49B4D3AF.7050705@intel.com \
    --to=xiaowei.yang@intel.com \
    --cc=keir.fraser@eu.citrix.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.