From: Ian Campbell <ian.campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: jgross@suse.com, xen-devel@lists.xenproject.org,
wei.liu2@citrix.com, jbeulich@suse.com,
chao.p.peng@linux.intel.com
Subject: Re: gnttab scalability and ticket locks status
Date: Fri, 26 Jun 2015 15:30:10 +0100 [thread overview]
Message-ID: <1435329010.32500.193.camel@citrix.com> (raw)
In-Reply-To: <558D5852.4040307@citrix.com>
On Fri, 2015-06-26 at 14:49 +0100, David Vrabel wrote:
> On 26/06/15 12:16, wei.liu2@citrix.com wrote:
> >
> > == Blocker ==
> >
> > == Hypervisor ==
> >
> > * gnttab: improve scalability (good)
> > - David Vrabel
>
> This is done.
>
> > * Use ticket lock in hypervisor (good)
> > - David Vrabel
>
> This needs the reverts reverting which is currently pending on a kernel
> update for ARM. If the kernel update doesn't turn up soon I think
> ticket locks should be re-added anyway since the failure wasn't really
> caused by the locking change (the netback bug had always been there).
As of flight 58875 the kernel is fixed everywhere we care about, I
think.
IOW I can't see a reason not to throw them back in right away.
Ian.
next prev parent reply other threads:[~2015-06-26 14:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 11:16 Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) wei.liu2
2015-06-26 11:27 ` Status of VM event patches (Was: Re: Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble)) Razvan Cojocaru
2015-06-26 11:32 ` Julien Grall
2015-06-26 11:34 ` Razvan Cojocaru
2015-06-26 12:06 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Vitaly Kuznetsov
2015-07-06 15:03 ` Wei Liu
2015-06-26 13:32 ` Jan Beulich
2015-06-26 13:49 ` gnttab scalability and ticket locks status David Vrabel
2015-06-26 14:30 ` Ian Campbell [this message]
2015-06-26 15:38 ` Jan Beulich
2015-06-26 13:50 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Andrew Cooper
2015-06-26 14:45 ` Daniel Kiper
2015-06-26 15:23 ` Status of VM event patches (Was: Re: Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble)) Razvan Cojocaru
2015-07-06 15:00 ` Wei Liu
2015-07-06 15:05 ` Razvan Cojocaru
2015-06-26 16:17 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Julien Grall
2015-06-30 2:30 ` Status of COLO (Was: Xen 4.6 Development Update) Yang Hongyang
2015-07-01 6:12 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Chen, Tiejun
2015-07-01 10:17 ` Julien Grall
2015-07-02 8:35 ` Ian Campbell
2015-07-02 8:51 ` Razvan Cojocaru
2015-07-02 10:32 ` Dario Faggioli
2015-07-01 10:01 ` Yu, Zhang
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=1435329010.32500.193.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=david.vrabel@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.