search for: spin_on_onw

Displaying 20 results from an estimated 27 matches for "spin_on_onw".

Did you mean: spin_on_onwer
2016 Jul 11
2
[PATCH v2 0/4] implement vcpu preempted check
...[kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > Paolo, could you help out with an (x86) KVM interface for this? > > Waiman, could you see if you can utilize this to get rid of the > SPIN_THRESHOLD in qspinlock_paravirt? That API is certainly useful to make the...
2016 Jul 11
2
[PATCH v2 0/4] implement vcpu preempted check
...[kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > Paolo, could you help out with an (x86) KVM interface for this? > > Waiman, could you see if you can utilize this to get rid of the > SPIN_THRESHOLD in qspinlock_paravirt? That API is certainly useful to make the...
2016 Jul 06
3
[PATCH v2 0/4] implement vcpu preempted check
...[kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > > Paolo, could you help out with an (x86) KVM interface for this? If it's just for spin loops, you can check if the version field in the steal time structure has changed. Paolo > Waiman, could you see if you c...
2016 Jul 06
3
[PATCH v2 0/4] implement vcpu preempted check
...[kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > > Paolo, could you help out with an (x86) KVM interface for this? If it's just for spin loops, you can check if the version field in the steal time structure has changed. Paolo > Waiman, could you see if you c...
2016 Jun 28
11
[PATCH v2 0/4] implement vcpu preempted check
..._raw_write_lock_irq 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is 2.49% sched-messaging [kernel.vmlinux] [k] system_call We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. These spin_on_onwer variant also cause rcu stall before we apply this patch set Pan Xinhui (4): kernel/sched: introduce vcpu preempted check interface powerpc/spinlock: support vcpu preempted check locking/osq: Drop the overload of osq_lock() kernel/locking: Drop the overload of {mutex,rwsem}_spin_on_owner...
2016 Jun 28
11
[PATCH v2 0/4] implement vcpu preempted check
..._raw_write_lock_irq 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is 2.49% sched-messaging [kernel.vmlinux] [k] system_call We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. These spin_on_onwer variant also cause rcu stall before we apply this patch set Pan Xinhui (4): kernel/sched: introduce vcpu preempted check interface powerpc/spinlock: support vcpu preempted check locking/osq: Drop the overload of osq_lock() kernel/locking: Drop the overload of {mutex,rwsem}_spin_on_owner...
2016 Jul 06
3
[PATCH v2 0/4] implement vcpu preempted check
...ner.is >>>> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >>>> >>>> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >>>> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >>>> These spin_on_onwer variant also cause rcu stall before we apply this patch set >>> >>> Paolo, could you help out with an (x86) KVM interface for this? >> >> If it's just for spin loops, you can check if the version field in the >> steal time structure has changed. > >...
2016 Jul 06
3
[PATCH v2 0/4] implement vcpu preempted check
...ner.is >>>> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >>>> >>>> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >>>> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >>>> These spin_on_onwer variant also cause rcu stall before we apply this patch set >>> >>> Paolo, could you help out with an (x86) KVM interface for this? >> >> If it's just for spin loops, you can check if the version field in the >> steal time structure has changed. > >...
2016 Jul 06
0
[PATCH v2 0/4] implement vcpu preempted check
...1% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is > 2.49% sched-messaging [kernel.vmlinux] [k] system_call > > We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin > loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. > These spin_on_onwer variant also cause rcu stall before we apply this patch set > Paolo, could you help out with an (x86) KVM interface for this? Waiman, could you see if you can utilize this to get rid of the SPIN_THRESHOLD in qspinlock_paravirt?
2016 Jul 06
0
[PATCH v2 0/4] implement vcpu preempted check
...[k] mutex_spin_on_owner.is >>> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >>> >>> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >>> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >>> These spin_on_onwer variant also cause rcu stall before we apply this patch set >>> >> >> Paolo, could you help out with an (x86) KVM interface for this? > > If it's just for spin loops, you can check if the version field in the > steal time structure has changed. Steal time will n...
2016 Jul 12
0
[PATCH v2 0/4] implement vcpu preempted check
..._on_owner.is >>> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >>> >>> We introduce interface bool vcpu_is_preempted(int cpu) and use it in >>> some spin >>> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >>> These spin_on_onwer variant also cause rcu stall before we apply this >>> patch set >>> >> Paolo, could you help out with an (x86) KVM interface for this? >> >> Waiman, could you see if you can utilize this to get rid of the >> SPIN_THRESHOLD in qspinlock_paravirt? > &gt...
2016 Jul 07
0
[PATCH v2 0/4] implement vcpu preempted check
...gt;> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >>>>> >>>>> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >>>>> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >>>>> These spin_on_onwer variant also cause rcu stall before we apply this patch set >>>> >>>> Paolo, could you help out with an (x86) KVM interface for this? >>> >>> If it's just for spin loops, you can check if the version field in the >>> steal time structure has...
2016 Oct 19
10
[PATCH v4 0/5] implement vcpu preempted check
..._raw_write_lock_irq 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is 2.49% sched-messaging [kernel.vmlinux] [k] system_call We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. These spin_on_onwer variant also cause rcu stall before we apply this patch set We also have observed some performace improvements. PPC test result: 1 copy - 0.94% 2 copy - 7.17% 4 copy - 11.9% 8 copy - 3.04% 16 copy - 15.11% details below: Without patch: 1 copy - File Write 4096 bufsize 8000 maxblocks 21...
2016 Oct 19
10
[PATCH v4 0/5] implement vcpu preempted check
..._raw_write_lock_irq 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is 2.49% sched-messaging [kernel.vmlinux] [k] system_call We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. These spin_on_onwer variant also cause rcu stall before we apply this patch set We also have observed some performace improvements. PPC test result: 1 copy - 0.94% 2 copy - 7.17% 4 copy - 11.9% 8 copy - 3.04% 16 copy - 15.11% details below: Without patch: 1 copy - File Write 4096 bufsize 8000 maxblocks 21...
2016 Jul 21
5
[PATCH v3 0/4] implement vcpu preempted check
...[k] _raw_write_lock_irq 3.02% sched-messaging [kernel.vmlinux] [k] system_call 2.69% sched-messaging [kernel.vmlinux] [k] wait_consider_task We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. These spin_on_onwer variant also cause rcu stall before we apply this patch set Pan Xinhui (4): kernel/sched: introduce vcpu preempted check interface powerpc/spinlock: support vcpu preempted check locking/osq: Drop the overhead of osq_lock() kernel/locking: Drop the overhead of {mutex,rwsem}_spin_on_owner...
2016 Jul 21
5
[PATCH v3 0/4] implement vcpu preempted check
...[k] _raw_write_lock_irq 3.02% sched-messaging [kernel.vmlinux] [k] system_call 2.69% sched-messaging [kernel.vmlinux] [k] wait_consider_task We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. These spin_on_onwer variant also cause rcu stall before we apply this patch set Pan Xinhui (4): kernel/sched: introduce vcpu preempted check interface powerpc/spinlock: support vcpu preempted check locking/osq: Drop the overhead of osq_lock() kernel/locking: Drop the overhead of {mutex,rwsem}_spin_on_owner...
2016 Oct 19
0
[PATCH v4 0/5] implement vcpu preempted check
...1% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is > 2.49% sched-messaging [kernel.vmlinux] [k] system_call > > We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin > loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. > These spin_on_onwer variant also cause rcu stall before we apply this patch set > > We also have observed some performace improvements. > > PPC test result: > > 1 copy - 0.94% > 2 copy - 7.17% > 4 copy - 11.9% > 8 copy - 3.04% > 16 copy - 15.11% > > details below: > Withou...
2016 Jul 06
4
[PATCH v2 0/4] implement vcpu preempted check
...[kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > > Paolo, could you help out with an (x86) KVM interface for this? Xen support of this interface should be rather easy. Could you please Cc: xen-devel-request at lists.xenproject.org in the next version? Juergen
2016 Jul 06
4
[PATCH v2 0/4] implement vcpu preempted check
...[kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > > Paolo, could you help out with an (x86) KVM interface for this? Xen support of this interface should be rather easy. Could you please Cc: xen-devel-request at lists.xenproject.org in the next version? Juergen
2016 Oct 19
0
[PATCH v4 0/5] implement vcpu preempted check
...1% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is > 2.49% sched-messaging [kernel.vmlinux] [k] system_call > > We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin > loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. > These spin_on_onwer variant also cause rcu stall before we apply this patch set > > We also have observed some performace improvements. > > PPC test result: > > 1 copy - 0.94% > 2 copy - 7.17% > 4 copy - 11.9% > 8 copy - 3.04% > 16 copy - 15.11% > > details below: > Withou...