[Bug 259940] [linuxulator][wine] no way to query the maximum process ki_size
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259940] [linuxulator][wine] no way to query the maximum process ki_size"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259940] [linuxulator][wine] no way to query the maximum process ki_size"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259940] [linuxulator][wine] no way to query the maximum process ki_size"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259940] [linuxulator][wine] no way to query the maximum process ki_size"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259940] [linuxulator][wine] no way to query the maximum process ki_size"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 20 Nov 2021 03:17:00 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259940 Bug ID: 259940 Summary: [linuxulator][wine] no way to query the maximum process ki_size Product: Base System Version: 13.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: damjan.jov@gmail.com "struct kinfo_proc" lets us query the maximum RSS size ever attained using "i_rusage.ru_maxrss", but there is no similar field for the maximum "ki_size" (size of all virtual memory). Since both Windows and Linux expect this, linuxulator's sys/compat/linprocfs/linprocfs.c function linprocfs_doprocstatus() completely omits "VmPeak", while in Wine I've had to lie that "ki_size" is both the current and maximum usage. I wonder whether the kernel even captures that statistic? -- You are receiving this mail because: You are the assignee for the bug.