[patch 3/3] LatencyTOP instrumentations part 2

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Arjan van de Ven <arjan@...>
Cc: Linux Kernel Mailing List <linux-kernel@...>, Linus Torvalds <torvalds@...>, Ingo Molnar <mingo@...>, Andrew Morton <akpm@...>
Date: Friday, January 18, 2008 - 1:42 pm

A few more high level annotations for LatencyTOP;
split into a separate patch since they're at a higher level
than the first part (and thus hide some lower level details
potentially, but could also obsolete several other low level
instrumentations)
---
 fs/read_write.c   |    7 ++++++-
 fs/readdir.c      |    4 +++-
 lib/kernel_lock.c |    3 +++
 3 files changed, 12 insertions(+), 2 deletions(-)

Index: linux-2.6.24-rc7/fs/read_write.c
===================================================================
--- linux-2.6.24-rc7.orig/fs/read_write.c
+++ linux-2.6.24-rc7/fs/read_write.c
@@ -255,6 +255,7 @@ EXPORT_SYMBOL(do_sync_read);
 
 ssize_t vfs_read(struct file *file, char __user *buf, size_t count, loff_t *pos)
 {
+	struct latency_entry reason;
 	ssize_t ret;
 
 	if (!(file->f_mode & FMODE_READ))
@@ -264,6 +265,7 @@ ssize_t vfs_read(struct file *file, char
 	if (unlikely(!access_ok(VERIFY_WRITE, buf, count)))
 		return -EFAULT;
 
+	set_latency_reason("Reading from file", &reason);
 	ret = rw_verify_area(READ, file, pos, count);
 	if (ret >= 0) {
 		count = ret;
@@ -281,6 +283,7 @@ ssize_t vfs_read(struct file *file, char
 		}
 	}
 
+	restore_latency_reason(&reason);
 	return ret;
 }
 
@@ -314,6 +317,7 @@ EXPORT_SYMBOL(do_sync_write);
 ssize_t vfs_write(struct file *file, const char __user *buf, size_t count, loff_t *pos)
 {
 	ssize_t ret;
+	struct latency_entry reason;
 
 	if (!(file->f_mode & FMODE_WRITE))
 		return -EBADF;
@@ -322,6 +326,7 @@ ssize_t vfs_write(struct file *file, con
 	if (unlikely(!access_ok(VERIFY_READ, buf, count)))
 		return -EFAULT;
 
+	set_latency_reason("Writing to file", &reason);
 	ret = rw_verify_area(WRITE, file, pos, count);
 	if (ret >= 0) {
 		count = ret;
@@ -338,7 +343,7 @@ ssize_t vfs_write(struct file *file, con
 			inc_syscw(current);
 		}
 	}
-
+	restore_latency_reason(&reason);
 	return ret;
 }
 
Index: linux-2.6.24-rc7/fs/readdir.c
===================================================================
--- linux-2.6.24-rc7.orig/fs/readdir.c
+++ linux-2.6.24-rc7/fs/readdir.c
@@ -21,6 +21,7 @@
 
 int vfs_readdir(struct file *file, filldir_t filler, void *buf)
 {
+	struct latency_entry reason;
 	struct inode *inode = file->f_path.dentry->d_inode;
 	int res = -ENOTDIR;
 	if (!file->f_op || !file->f_op->readdir)
@@ -29,7 +30,7 @@ int vfs_readdir(struct file *file, filld
 	res = security_file_permission(file, MAY_READ);
 	if (res)
 		goto out;
-
+	set_latency_reason("Unlinking file", &reason);
 	mutex_lock(&inode->i_mutex);
 	res = -ENOENT;
 	if (!IS_DEADDIR(inode)) {
@@ -37,6 +38,7 @@ int vfs_readdir(struct file *file, filld
 		file_accessed(file);
 	}
 	mutex_unlock(&inode->i_mutex);
+	restore_latency_reason(&reason);
 out:
 	return res;
 }
Index: linux-2.6.24-rc7/lib/kernel_lock.c
===================================================================
--- linux-2.6.24-rc7.orig/lib/kernel_lock.c
+++ linux-2.6.24-rc7/lib/kernel_lock.c
@@ -64,15 +64,18 @@ void __lockfunc __release_kernel_lock(vo
  */
 void __lockfunc lock_kernel(void)
 {
+	struct latency_entry reason;
 	struct task_struct *task = current;
 	int depth = task->lock_depth + 1;
 
+	set_latency_reason("Big kernel lock contention", &reason);
 	if (likely(!depth))
 		/*
 		 * No recursion worries - we set up lock_depth _after_
 		 */
 		down(&kernel_sem);
 
+	restore_latency_reason(&reason);
 	task->lock_depth = depth;
 }
 
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[Announce] Development release 0.1 of the LatencyTOP tool, Arjan van de Ven, (Fri Jan 18, 1:36 pm)
Re: Development release 0.1 of the LatencyTOP tool, KOSAKI Motohiro, (Sun Jan 20, 8:52 pm)
Re: [Announce] Development release 0.1 of the LatencyTOP tool, Arjan van de Ven, (Sat Jan 19, 1:16 am)
Re: [Announce] Development release 0.1 of the LatencyTOP tool, Arjan van de Ven, (Sat Jan 19, 1:25 am)
Re: [Announce] Development release 0.1 of the LatencyTOP tool, Arjan van de Ven, (Sat Jan 19, 1:34 am)
Re: [Announce] Development release 0.1 of the LatencyTOP tool, Arjan van de Ven, (Fri Jan 18, 2:35 pm)
[patch 3/3] LatencyTOP instrumentations part 2, Arjan van de Ven, (Fri Jan 18, 1:42 pm)
[patch 2/3] Latencytop instrumentations part 1, Arjan van de Ven, (Fri Jan 18, 1:40 pm)
Re: [patch 2/3] Latencytop instrumentations part 1, Frank Ch. Eigler, (Fri Jan 18, 6:26 pm)
Re: [patch 2/3] Latencytop instrumentations part 1, Arjan van de Ven, (Fri Jan 18, 6:33 pm)
Re: [patch 2/3] Latencytop instrumentations part 1, Frank Ch. Eigler, (Fri Jan 18, 7:11 pm)
Re: [patch 2/3] Latencytop instrumentations part 1, Arjan van de Ven, (Fri Jan 18, 7:20 pm)
Re: [patch 2/3] Latencytop instrumentations part 1, Arnaldo Carvalho de Melo, (Fri Jan 18, 6:47 pm)
[patch 1/3] LatencyTOP infrastructure patch, Arjan van de Ven, (Fri Jan 18, 1:39 pm)
Re: LatencyTOP infrastructure patch, KOSAKI Motohiro, (Mon Jan 21, 4:06 am)
Re: LatencyTOP infrastructure patch, Arjan van de Ven, (Mon Jan 21, 12:16 pm)
Re: [patch 1/3] LatencyTOP infrastructure patch, Dmitry Adamushko, (Sun Jan 20, 12:47 pm)
Re: [patch 1/3] LatencyTOP infrastructure patch, Dmitry Adamushko, (Sun Jan 20, 1:18 pm)