From: Andi Kleen <andi@firstfloor.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC] get_write_access()/deny_write_access() without inode->i_lock
Date: Mon, 20 Jun 2011 12:47:54 -0700 [thread overview]
Message-ID: <m21uyoffo5.fsf@firstfloor.org> (raw)
In-Reply-To: <20110619235147.GQ11521@ZenIV.linux.org.uk> (Al Viro's message of "Mon, 20 Jun 2011 00:51:47 +0100")
Al Viro <viro@ZenIV.linux.org.uk> 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@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2011-06-20 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 23:51 [RFC] get_write_access()/deny_write_access() without inode->i_lock Al Viro
2011-06-20 12:47 ` David Howells
2011-06-20 13:18 ` Al Viro
2011-06-20 13:20 ` David Howells
2011-06-20 13:20 ` David Howells
2011-06-20 13:21 ` Frantisek Hrbata
2011-06-20 14:15 ` Al Viro
2011-06-20 15:55 ` Linus Torvalds
2011-06-20 15:55 ` Linus Torvalds
2011-06-20 16:13 ` Al Viro
2011-06-20 16:22 ` Linus Torvalds
2011-06-20 16:42 ` Al Viro
2011-06-20 17:03 ` Al Viro
2011-06-20 19:47 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21uyoffo5.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.