Lines Matching refs:system

14  * Understanding system resources necessary to build and run a workload
16  * Linux tracing and strace can be used to discover the system resources
17    in use by a workload. The completeness of the system usage information
19  * Performance and security of the operating system can be analyzed with
32 the system resources in use by a workload. Once we discover and understand
36 This method of tracing using strace tells us the system calls invoked by
37 the workload and doesn't include all the system calls that can be invoked
39 these system calls that are invoked. As an example, if a workload opens a
41 is traced. Any error paths in that system call will not be traced. If there
44 of the system usage information depends on the completeness of coverage of a
47 The goal is tracing a workload on a system running a default kernel without
50 How do we gather fine-grained system information?
53 strace tool can be used to trace system calls made by a process and signals
55 application and the operating system kernel. They enable a program to
56 request services from the kernel. For instance, the open() system call in
57 Linux is used to provide access to a file in the file system. strace enables
58 us to track all the system calls made by an application. It lists all the
59 system calls made by a process and their resulting output.
65 to gather fine-grained information on a workload's usage of system resources.
71 Getting the system ready for tracing
74 Before we can get started we will show you how to get your system ready.
75 We assume that you have a Linux distribution running on a physical system
82 scripts/ver_linux is a good way to check if your system already has
111 system calls. This allows us to easily measure the impact of changes,
122 CPU, CPU cache, devices, I/O, interrupts, file system, memory, network,
123 operating system, pipelines, schedulers, and virtual machines. Please refer
143 and debugging tool and can be used to discover the system resources in use
151  * For troubleshooting various problems related to the operating system.
154 errors for each system call and report a summary when program exits,
155 suppressing the regular output. This attempts to show system time (CPU time
157 these features to get information on workload system usage.
160 run in verbose mode gives more detailed information about the system calls
164 system call, the total time in seconds, the microseconds per call, the total
165 number of calls, the count of each system call that has failed with an error
166 and the type of system call made.
188 We can use cscope to find which system call belongs to which subsystem.
211 exported by the kernel. It is very useful for profiling the system and
241 system calls. This allows us to easily measure the impact of changes,
260 are available for CPU, CPU cache, devices, I/O, interrupts, file system,
261 memory, network, operating system, pipelines, schedulers, and virtual
326 The below table shows the system calls invoked by the workload, number of
327 times each system call is invoked, and the corresponding Linux subsystem.
436 The below table shows the system calls invoked by the workload, number of
437 times each system call is invoked, and the corresponding Linux subsystem.
530 The below table shows the system calls invoked by the workload, number of
531 times each system call is invoked, and the corresponding Linux subsystem.
606 …* `Monitoring and managing system status and performance <https://access.redhat.com/documentation/…