| 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
| ||
|
Date: Wed, 3 Dec 2014 09:21:18 +0100 From: Jan Kara <jack@...e.cz> To: Theodore Ts'o <tytso@....edu> Cc: Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org, Zheng Liu <wenqing.lz@...bao.com> Subject: Re: [PATCH 0/7 v4] ext4: Extent status tree shrinker improvements On Tue 02-12-14 21:20:18, Ted Tso wrote: > I realized I hadn't ack'ed this patch series, but since this patch > series is an improvement on what we have now, I've included them in > the ext4 git tree. I'm sure there's more improvements we can do on > the shrinker, but we can use these patches as a starting point. Yeah, I'd like to return to this as well. In particular it should be relatively straightforward to RCUify the list of inodes with extents to shrink and thus avoid the relatively expensive s_es_lock in the shrinker. Additionally we could batch removal from the list of inodes with reclaimable extents (removal would happen only in the ext4_evict_inode() and in the shrinker when it sees say 16 inodes with zero reclaimable extents in the list - then it would grab the lock, scan part of the list and remove all inodes with zero reclaimable extents). I'd expect that to significantly reduce contention on s_es_lock. But these need more measurements and experimentation... Honza -- Jan Kara <jack@...e.cz> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists