lkml.org 
[lkml]   [2015]   [Apr]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH 2/2] locking/rwsem: Use a return variable in rwsem_spin_on_owner()
From
On Thu, Apr 9, 2015 at 11:08 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> The pointer is a known-safe kernel pointer - it's just that it was
> "known safe" a few instructions ago, and might be rcu-free'd at any
> time.

Actually, we could even do something like this:

static inline int sem_owner_on_cpu(struct semaphore *sem, struct
task_struct *owner)
{
int on_cpu;

#ifdef CONFIG_DEBUG_PAGEALLOC
rcu_read_lock();
#endif
on_cpu = sem->owner == owner && owner->on_cpu;
#ifdef CONFIG_DEBUG_PAGEALLOC
rcu_read_unlock();
#endif
return on_cpu;
}

because we really don't need to hold the RCU lock over the whole loop,
we just need to validate that the semaphore owner still matches, and
if so, check that it's on_cpu.

And if CONFIG_DEBUG_PAGEALLOC is set, we don't care about performance
*at*all*. We will have worse performance problems than doing some RCU
read-locking inside the loop.

And if CONFIG_DEBUG_PAGEALLOC isn't set, we don't really care about
locking, since at worst we just access stale memory for one iteration.

Hmm. It's not pretty, but neither is the current "let's just take a
rcu lock that we don't really need over a loop that doesn't have very
strict bounding".

Comments?

Linus


\
 
 \ /
  Last update: 2015-04-09 20:41    [W:1.568 / U:0.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site