linux-kernel - [patch 00/27] [rfc] vfs scalability patchset

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090425012020.457460929@suse.de>
Date:	Sat, 25 Apr 2009 11:20:20 +1000
From:	npiggin@...e.de
To:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [patch 00/27] [rfc] vfs scalability patchset

Here is my current patchset for improving vfs locking scalability. Since
last posting, I have fixed several bugs, solved several more problems, and
done an initial sweep of filesystems (autofs4 is probably the trickiest,
and unfortunately I don't have a good test setup here for that yet, but
at least I've looked through it).

Also started to tackle files_lock, vfsmount_lock, and inode_lock.
(I included my mnt_want_write patches before the vfsmount_lock scalability
stuff because that just made it a bit easier...). These appear to be the
problematic global locks in the vfs.

It's running stably here so far on basic stress testing here on several file
systems (xfs, tmpfs, ext?). But it still might eat your data of course.

Would be very interested in any feedback.

Thanks,
Nick

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