linux-kernel - [PATCH 0/5] nilfs2: introduce tracepoints

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: <1444153828-6747-1-git-send-email-konishi.ryusuke@lab.ntt.co.jp>
Date:	Wed,  7 Oct 2015 02:50:23 +0900
From:	Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Hitoshi Mitake <mitake.hitoshi@....ntt.co.jp>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-nilfs <linux-nilfs@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp>
Subject: [PATCH 0/5] nilfs2: introduce tracepoints 

Hi Andrew,

Please queue the following changes for the next merge window:

Hitoshi Mitake (4):
      nilfs2: add a tracepoint for tracking stage transition of segment construction
      nilfs2: add a tracepoint for transaction events
      nilfs2: add tracepoints for analyzing sufile manipulation
      nilfs2: add tracepoints for analyzing reading and writing metadata files

Ryusuke Konishi (1):
      MAINTAINERS: nilfs2: add header file for tracing

These introduces some tracepoints to nilfs2 to help tracking its
behavior for bottleneck detection, debugging, etc.

Thanks,
Ryusuke Konishi
--

 MAINTAINERS                   |   1 +
 fs/nilfs2/mdt.c               |   6 ++
 fs/nilfs2/segment.c           | 104 ++++++++++++++++----
 fs/nilfs2/segment.h           |   3 +-
 fs/nilfs2/sufile.c            |   8 ++
 include/trace/events/nilfs2.h | 224 ++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 324 insertions(+), 22 deletions(-)

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