| 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: <1357749908-16562-1-git-send-email-tj@kernel.org> Date: Wed, 9 Jan 2013 08:45:03 -0800 From: Tejun Heo <tj@...nel.org> To: axboe@...nel.dk Cc: linux-kernel@...r.kernel.org, chavey@...gle.com Subject: [PATCHSET] block: improve tracepoints Hello, Jens. This patchset fixes/improves bio_complete TP so that block layer proper triggers for all completing bios instead of stackign drivers triggering them manually and adds more buffer / block / writeback TPs. These improve visibility in general and are already in use in google. This patchset contains the following five patches. 0001-block-add-missing-block_bio_complete-tracepoint.patch 0002-block-add-req-to-bio_-front-back-_merge-tracepoints.patch 0003-buffer-make-touch_buffer-an-exported-function.patch 0004-block-add-block_touch_buffer-tracepoint.patch 0005-writeback-add-more-tracepoints.patch It's based on top of v3.8-rc2 and also available in the following git branch. git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git block-tps diffstat follows. Thanks. block/blk-core.c | 5 - drivers/md/dm.c | 1 drivers/md/raid5.c | 11 --- fs/bio.c | 2 fs/buffer.c | 8 ++ fs/fs-writeback.c | 17 ++++ include/linux/blktrace_api.h | 1 include/linux/buffer_head.h | 2 include/trace/events/block.h | 78 ++++++++++++++++++---- include/trace/events/writeback.h | 135 +++++++++++++++++++++++++++++++++++++++ kernel/trace/blktrace.c | 28 +++++++- mm/page-writeback.c | 2 12 files changed, 255 insertions(+), 35 deletions(-) -- tejun -- 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/
Powered by blists - more mailing lists