This reverts commit ad4b32c45d as it
conflicts with upstream changes in 6.13-rc1. If this is still really
needed, it can come back after 6.13-rc1 is merged, but really, this
whole uid_sys_stats thing should just be a bpf program instead of this
constantly-out-of-tree code that has merge conflicts all the time...
Bug: 120442023
Cc: Jin Qian <jinqian@google.com>
Cc: Amit Pundir <amit.pundir@linaro.org>
Cc: Alistair Strachan <astrachan@google.com>
Change-Id: I459a66abdeea936ce88e58e17d64e9e657c4e7ec
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
47 lines
1.1 KiB
C
47 lines
1.1 KiB
C
/* SPDX-License-Identifier: GPL-2.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 */
|
|
};
|