linux-kernel - Re: [rfc] scale dcache locking

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090401142312.GD28946@ZenIV.linux.org.uk>
Date:	Wed, 1 Apr 2009 15:23:12 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	npiggin@...e.de
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [rfc] scale dcache locking

On Mon, Mar 30, 2009 at 02:55:39AM +1100, npiggin@...e.de wrote:
> This is my sketch for improving dcache locking scalability. So far I've
> only really been looking at core code to get an idea of how it might look,
> so most configurable functionality is broken (and unfortunately it might
> well be something in there which will cause a fundamental problem for me).

Umm...  Some of that makes obvious sense per se, some...  In particular,
all of a sudden we get contention between multiple dput() on the same
dentry, which is dirt-common for directory ones.
--
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/