Re: [PATCH 0/4] seqlock: Add new blocking reader type & use rwlock

2013-08-23 Thread Waiman Long
On 07/03/2013 09:52 PM, Waiman Long wrote: During some perf-record sessions of the kernel running the high_systime workload of the AIM7 benchmark, it was found that quite a large portion of the spinlock contention was due to the perf_event_mmap_event() function itself. This perf kernel function

Re: [PATCH 0/4] seqlock: Add new blocking reader type use rwlock

2013-08-23 Thread Waiman Long
On 07/03/2013 09:52 PM, Waiman Long wrote: During some perf-record sessions of the kernel running the high_systime workload of the AIM7 benchmark, it was found that quite a large portion of the spinlock contention was due to the perf_event_mmap_event() function itself. This perf kernel function

[PATCH 0/4] seqlock: Add new blocking reader type & use rwlock

2013-07-03 Thread Waiman Long
During some perf-record sessions of the kernel running the high_systime workload of the AIM7 benchmark, it was found that quite a large portion of the spinlock contention was due to the perf_event_mmap_event() function itself. This perf kernel function calls d_path() which, in turn, call

[PATCH 0/4] seqlock: Add new blocking reader type use rwlock

2013-07-03 Thread Waiman Long
During some perf-record sessions of the kernel running the high_systime workload of the AIM7 benchmark, it was found that quite a large portion of the spinlock contention was due to the perf_event_mmap_event() function itself. This perf kernel function calls d_path() which, in turn, call