| 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: <CA+nQAmakcohVNJJ6fFhRG835WYq76_hDr5eTX+_ui2b+LNHf6A@mail.gmail.com> Date: Sun, 12 Oct 2014 04:30:20 -0700 From: Nick R <reddyn.lists@...il.com> To: linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: how does one figure out I/O bottlenecks between 2 version of the kernel? Hi I am new new at this....Sorry if I missed something obvious.. I have been asked a few times to figure out bottlenecks in I/O that cause benchmark scores to degrade between two builds of the kernel... (new build which has a few thousand commits seems to have a worse I/O performance number than the old build). Often times I end up spending time trying a bisect or reverting commits to check if they were the cause ..and after is usually found to be some commit in the storage driver or some other module ...and not the filesystem. What would be the best way to profile where the bottleneck is in I/O? Are there built in profiling options? I tried turning on ext4 events but that itself seems to add to the performance overhead...Also couldnt figure out how to use the data.. Or is there a nice way to prove that the filesystem is not the cause? I am fairly new to this and might be missing out on something obvious.. Sorry if I was not supposed to mail directly... Please let me know. Thanks Nick -- 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