Re: [PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-08-05 Thread Raghavendra K T
On 08/06/2013 04:20 AM, H. Peter Anvin wrote: So, having read through the entire thread I *think* this is what the status of this patchset is: 1. Patches 1-17 are noncontroversial, Raghavendra is going to send an update split into two patchsets; Yes. Only one patch would be common to

Re: [PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-08-05 Thread H. Peter Anvin
So, having read through the entire thread I *think* this is what the status of this patchset is: 1. Patches 1-17 are noncontroversial, Raghavendra is going to send an update split into two patchsets; 2. There are at least two versions of patch 15; I think the "PATCH RESEND RFC" is the right

Re: [PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-08-05 Thread H. Peter Anvin
So, having read through the entire thread I *think* this is what the status of this patchset is: 1. Patches 1-17 are noncontroversial, Raghavendra is going to send an update split into two patchsets; 2. There are at least two versions of patch 15; I think the PATCH RESEND RFC is the right

Re: [PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-08-05 Thread Raghavendra K T
On 08/06/2013 04:20 AM, H. Peter Anvin wrote: So, having read through the entire thread I *think* this is what the status of this patchset is: 1. Patches 1-17 are noncontroversial, Raghavendra is going to send an update split into two patchsets; Yes. Only one patch would be common to

Re: [PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-07-22 Thread Raghavendra K T
On 07/23/2013 01:06 AM, Konrad Rzeszutek Wilk wrote: github link: https://github.com/ktraghavendra/linux/tree/pvspinlock_v11 And chance you have a backup git tree? I get: This repository is temporarily unavailable. I only have it on local apart from there :(. Hope it was a temporary github

Re: [PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-07-22 Thread Konrad Rzeszutek Wilk
> > github link: https://github.com/ktraghavendra/linux/tree/pvspinlock_v11 And chance you have a backup git tree? I get: This repository is temporarily unavailable. > > Please note that we set SPIN_THRESHOLD = 32k with this series, > that would eatup little bit of overcommit performance of

[PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-07-22 Thread Raghavendra K T
This series replaces the existing paravirtualized spinlock mechanism with a paravirtualized ticketlock mechanism. The series provides implementation for both Xen and KVM. Changes in V11: - use safe_halt in lock_spinning path to avoid potential problem in case of irq_handlers taking lock in

[PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-07-22 Thread Raghavendra K T
This series replaces the existing paravirtualized spinlock mechanism with a paravirtualized ticketlock mechanism. The series provides implementation for both Xen and KVM. Changes in V11: - use safe_halt in lock_spinning path to avoid potential problem in case of irq_handlers taking lock in

Re: [PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-07-22 Thread Konrad Rzeszutek Wilk
github link: https://github.com/ktraghavendra/linux/tree/pvspinlock_v11 And chance you have a backup git tree? I get: This repository is temporarily unavailable. Please note that we set SPIN_THRESHOLD = 32k with this series, that would eatup little bit of overcommit performance of PLE

Re: [PATCH RFC V11 0/18] Paravirtualized ticket spinlocks

2013-07-22 Thread Raghavendra K T
On 07/23/2013 01:06 AM, Konrad Rzeszutek Wilk wrote: github link: https://github.com/ktraghavendra/linux/tree/pvspinlock_v11 And chance you have a backup git tree? I get: This repository is temporarily unavailable. I only have it on local apart from there :(. Hope it was a temporary github