linux-kernel - [PATCH 0/9] Sync and VFS scalability improvements

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: <1426016724-23912-1-git-send-email-jbacik@fb.com>
Date:	Tue, 10 Mar 2015 15:45:15 -0400
From:	Josef Bacik <jbacik@...com>
To:	<linux-fsdevel@...r.kernel.org>, <david@...morbit.com>,
	<viro@...iv.linux.org.uk>, <jack@...e.cz>,
	<linux-kernel@...r.kernel.org>
Subject: [PATCH 0/9] Sync and VFS scalability improvements

These are patches that Dave Chinner wrote two years ago that are still very much
needed today.  I recently ran into a problem where I had millions of inodes that
needed to be evicted at unmount time and it soft locked up the box and kept any
other file system from doing work.  These patches fix this problem by breaking
the inode_sb_list_lock into per-sb, and then converting the per sb inode list
into a list_lru for better scalability.

I've also pulled forward Dave's sync scalability patches which still seem pretty
relevant.  I had to fix a couple of these to bring them forward but I touched
very little and I've preserved the authorship of everything.  I added the
Reviewed-by's that were there when the patches were originally submitted.  I've
run this through xfstests on btrfs and xfs and verified that everything seems to
be working.  If you are interested the original submission can be found here

http://lwn.net/Articles/561569/

Finally the last patch is from me and this fixes the softlockup problems I was
seeing on unmount with a large amount of inodes that needed to be evicted.
Thanks,

Josef

--
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/