xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: John Weekes <lists.xen@nuclearfallout.net>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests
Date: Mon, 07 Mar 2011 11:33:08 -0800	[thread overview]
Message-ID: <4D7532F4.40705@nuclearfallout.net> (raw)
In-Reply-To: <1299230127.6552.149.camel@zakaz.uk.xensource.com>

On 3/4/2011 1:15 AM, Ian Campbell wrote:
> This series was for more recent kernels. It seems to backport with
> minimum fuss (switch from __this_cpu_(read|write) to __get_cpu_var).
>
> I only compile tested this one file and haven't even booted it but the
> result is available on top of xen.git xen/next-2.6.32 at:
> ...
>    git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness-2.6.32

Thanks for the rebase and for the earlier instructions on how to merge 
your git topic branch, which were clear and easy to follow.

I've have this code running on a lightly-used production machine right 
now with no problems observed so far. I will continue to monitor and 
roll it out to a higher-usage machine that has had problems without the 
RR bits within the next few days, if all goes well.

-John

  reply	other threads:[~2011-03-07 19:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  2:25 unfair servicing of DomU vbd requests James Harper
2011-03-03  7:29 ` Keir Fraser
2011-03-03  8:22   ` Ian Campbell
2011-03-03  8:28     ` James Harper
2011-03-03  8:30       ` Keir Fraser
2011-03-03 17:09         ` [GIT/PATCH 0/5] " Ian Campbell
2011-03-03 17:10           ` [PATCH 1/5] xen: events: Process event channels notifications in round-robin order Ian Campbell
2011-03-03 17:10           ` [PATCH 2/5] xen: events: Make last processed event channel a per-cpu variable Ian Campbell
2011-03-09 20:32             ` Konrad Rzeszutek Wilk
2011-03-09 20:40               ` Ian Campbell
2011-03-09 20:47                 ` Jeremy Fitzhardinge
2011-03-10  8:30                   ` Ian Campbell
2011-03-11 17:46                     ` Jeremy Fitzhardinge
2011-03-03 17:10           ` [PATCH 3/5] xen: events: Clean up round-robin evtchn scan Ian Campbell
2011-03-03 17:10           ` [PATCH 4/5] xen: events: Make round-robin scan fairer by snapshotting each l2 word Ian Campbell
2011-03-03 17:10           ` [PATCH 5/5] xen: events: Remove redundant clear of l2i at end of round-robin loop Ian Campbell
2011-03-04  8:40           ` [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests John Weekes
2011-03-04  9:15             ` Ian Campbell
2011-03-07 19:33               ` John Weekes [this message]
     [not found] <AEC6C66638C05B468B556EA548C1A77D01C55BC6@trantor>
2011-03-04  7:12 ` MaoXiaoyun
2011-03-04  7:21   ` Ian Campbell
2011-03-04  9:59     ` MaoXiaoyun
2011-03-04 10:06       ` Ian Campbell
2011-03-07  3:37         ` MaoXiaoyun
2011-03-07  8:09           ` Ian Campbell
2011-03-07 10:20             ` MaoXiaoyun
2011-03-08  2:04 ` MaoXiaoyun
2011-03-08  2:22   ` James Harper
     [not found]   ` <AEC6C66638C05B468B556EA548C1A77D01C55D47@trantor>
2011-03-09  5:38     ` MaoXiaoyun

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=4D7532F4.40705@nuclearfallout.net \
    --to=lists.xen@nuclearfallout.net \
    --cc=Ian.Campbell@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 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).