From 871480933a1c28f8a9fed4c4d34d06c439a7a422 Mon Sep 17 00:00:00 2001
From: Srikant Patnaik
Date: Sun, 11 Jan 2015 12:28:04 +0530
Subject: Moved, renamed, and deleted files
The original directory structure was scattered and unorganized.
Changes are basically to make it look like kernel structure.
---
ANDROID_3.4.5/include/linux/task_io_accounting.h | 45 ------------------------
1 file changed, 45 deletions(-)
delete mode 100644 ANDROID_3.4.5/include/linux/task_io_accounting.h
(limited to 'ANDROID_3.4.5/include/linux/task_io_accounting.h')
diff --git a/ANDROID_3.4.5/include/linux/task_io_accounting.h b/ANDROID_3.4.5/include/linux/task_io_accounting.h
deleted file mode 100644
index bdf855c2..00000000
--- a/ANDROID_3.4.5/include/linux/task_io_accounting.h
+++ /dev/null
@@ -1,45 +0,0 @@
-/*
- * task_io_accounting: a structure which is used for recording a single task's
- * IO statistics.
- *
- * Don't include this header file directly - it is designed to be dragged in via
- * sched.h.
- *
- * Blame Andrew Morton for all this.
- */
-
-struct task_io_accounting {
-#ifdef CONFIG_TASK_XACCT
- /* bytes read */
- u64 rchar;
- /* bytes written */
- u64 wchar;
- /* # of read syscalls */
- u64 syscr;
- /* # of write syscalls */
- u64 syscw;
-#endif /* CONFIG_TASK_XACCT */
-
-#ifdef CONFIG_TASK_IO_ACCOUNTING
- /*
- * The number of bytes which this task has caused to be read from
- * storage.
- */
- u64 read_bytes;
-
- /*
- * The number of bytes which this task has caused, or shall cause to be
- * written to disk.
- */
- u64 write_bytes;
-
- /*
- * A task can cause "negative" IO too. If this task truncates some
- * dirty pagecache, some IO which another task has been accounted for
- * (in its write_bytes) will not be happening. We _could_ just
- * subtract that from the truncating task's write_bytes, but there is
- * information loss in doing that.
- */
- u64 cancelled_write_bytes;
-#endif /* CONFIG_TASK_IO_ACCOUNTING */
-};
--
cgit