| 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
| ||
|
Message-ID: <534D5E02.6030500@hp.com> Date: Tue, 15 Apr 2014 10:27:46 -0600 From: Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@...com> To: Jan Kara <jack@...e.cz> CC: T Makphaibulchoke <tmac@...com>, tytso@....edu, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, aswin@...com Subject: Re: [PATCH v2] fs/ext4: increase parallelism in updating ext4 orphan list On 04/14/2014 11:40 AM, Jan Kara wrote: > Thanks for trying that out! Can you please send me a patch you have been > testing? Because it doesn't quite make sense to me why using i_mutex should > be worse than using hashed locks... > Thanks again for the comments. Since i_mutex is also used for serialization in other operations on an inode, in the case that the i_mutex is not held using it for serialization could cause contention with other operations on the inode. As the number shows substantial instances of orphan add or delete calls without holding the i_mutex, I presume the performance degradation is due to the contention. As for the patch, could you please let me know if you need the patch using i_mutex or the patch I'm planning to submit. If it's the latter, I'm thinking of go ahead and resubmit it. Thanks, Mak. > OK, at least that makes sense. > > Honza > -- 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