Bug 1267803 - systemd-cgtop: CPU usage per user slice does not show
systemd-cgtop: CPU usage per user slice does not show
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd (Show other bugs)
7.1
x86_64 Linux
medium Severity medium
: rc
: ---
Assigned To: systemd-maint
qe-baseos-daemons
:
Depends On:
Blocks: 1297395 1298243 1420851
  Show dependency treegraph
 
Reported: 2015-10-01 01:27 EDT by Susant Sahani
Modified: 2018-04-11 17:27 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Susant Sahani 2015-10-01 01:27:57 EDT
Description of problem:
When running systemd-cgtop onls shows CPU usage for the '/' path. It does not show CPU usage per user slice. Seeing the IO and memory stats per slice is desirable as well

Version-Release number of selected component (if applicable):
RHEL7.1 x86_64

How reproducible:

always occurs

Actual results:

slice does not show CPU usage

Expected results:
slice should show CPU usage
Comment 2 Susant Sahani 2015-10-01 02:03:10 EDT
Path                                         Tasks   %CPU   Memory  Input/s Output/s

user.slice/user-0.slice/session-273.scope   2      -        -        -        -
/user.slice/user-0.slice/session-375.scope  6      -        -        -        


This woks on fedora

Fedora 23:
systemd-222-6.fc23.x86_64
systemd-compat-libs-222-6.fc23.x86_64
systemd-devel-222-6.fc23.x86_64
systemd-journal-gateway-222-6.fc23.x86_64
systemd-libs-222-6.fc23.x86_64


Path                                       Tasks   %CPU   Memory  Input/s Output/s
/user.slice/user-1000.slice                  79    7.0        -        -        -
/system.slice                              -    1.6   664.8M        -        -

Note You need to log in before you can comment on or make changes to this bug.