Re: [RFC] get_write_access()/deny_write_access() without inode->i_lock

[Andi Kleen]

Al Viro <viro@xxxxxxxxxxxxxxxxxx> writes:

> 	I'm seriously tempted to throw away i_lock uses in
> {get,deny}_write_access(), as in the patch below.  The question is, how

Are there any known workload where the spinlock contends badly here?
Or what's the motivation for it?

Thanks,

-Andi

-- 
ak@xxxxxxxxxxxxxxx -- Speaking for myself only
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/