From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: Alexander Viro <viro@math.psu.edu>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: open-scale-2.6.2-A0
Date: Wed, 11 Feb 2004 12:58:28 +0100 [thread overview]
Message-ID: <20040211115828.GA13868@elte.hu> (raw)
[-- Attachment #1: Type: text/plain, Size: 176 bytes --]
i've attached an obvious scalability improvement for write()s. We in
essence used a system-global lock for every open(WRITE) - argh!
Compiles & boots fine on x86 SMP.
Ingo
[-- Attachment #2: inode-scale-2.6.2-A0 --]
[-- Type: text/plain, Size: 1489 bytes --]
--- linux/fs/namei.c.orig2
+++ linux/fs/namei.c
@@ -238,30 +238,34 @@ int permission(struct inode * inode,int
* except for the cases where we don't hold i_writecount yet. Then we need to
* use {get,deny}_write_access() - these functions check the sign and refuse
* to do the change if sign is wrong. Exclusion between them is provided by
- * spinlock (arbitration_lock) and I'll rip the second arsehole to the first
- * who will try to move it in struct inode - just leave it here.
+ * the inode->i_lock spinlock.
*/
-static spinlock_t arbitration_lock = SPIN_LOCK_UNLOCKED;
+
int get_write_access(struct inode * inode)
{
- spin_lock(&arbitration_lock);
+ spin_lock(&inode->i_lock);
if (atomic_read(&inode->i_writecount) < 0) {
- spin_unlock(&arbitration_lock);
+ spin_unlock(&inode->i_lock);
return -ETXTBSY;
}
atomic_inc(&inode->i_writecount);
- spin_unlock(&arbitration_lock);
+ spin_unlock(&inode->i_lock);
+
return 0;
}
+
int deny_write_access(struct file * file)
{
- spin_lock(&arbitration_lock);
- if (atomic_read(&file->f_dentry->d_inode->i_writecount) > 0) {
- spin_unlock(&arbitration_lock);
+ struct inode *inode = file->f_dentry->d_inode;
+
+ spin_lock(&inode->i_lock);
+ if (atomic_read(&inode->i_writecount) > 0) {
+ spin_unlock(&inode->i_lock);
return -ETXTBSY;
}
- atomic_dec(&file->f_dentry->d_inode->i_writecount);
- spin_unlock(&arbitration_lock);
+ atomic_dec(&inode->i_writecount);
+ spin_unlock(&inode->i_lock);
+
return 0;
}
next reply other threads:[~2004-02-11 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 11:58 Ingo Molnar [this message]
2004-02-11 12:20 ` open-scale-2.6.2-A0 Jamie Lokier
2004-02-11 12:27 ` open-scale-2.6.2-A0 Ingo Molnar
2004-02-11 12:45 ` open-scale-2.6.2-A0 Jamie Lokier
2004-02-11 20:39 ` open-scale-2.6.2-A0 Andrew Morton
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=20040211115828.GA13868@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@math.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox