From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: James Harper <james.harper@bendigoit.com.au>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.xen@gmail.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 2/5] xen: events: Make last processed event channel a per-cpu variable.
Date: Fri, 11 Mar 2011 09:46:33 -0800 [thread overview]
Message-ID: <4D7A5FF9.9080807@goop.org> (raw)
In-Reply-To: <1299745807.17339.710.camel@zakaz.uk.xensource.com>
On 03/10/2011 12:30 AM, Ian Campbell wrote:
> More importantly I don't think it's a big enough deal to be worth
> respinning the series
Definitely not.
J
next prev parent reply other threads:[~2011-03-11 17:46 UTC|newest]
Thread overview: 19+ 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 [this message]
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
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=4D7A5FF9.9080807@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.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.