New answers tagged

0

This is my silly mistake I am adding here instead of deleting , in case someone also does this mistake comm %s The filename of the executable, in parentheses. This is visible whether or not the executable is swapped out. If comm has space/s, No of fields differ and 39th field doesn't remain 39th being ...


1

The documentation says they are in "jiffies", but the documentation is wrong. Try running a CPU-intensive task and sampling the counters a few seconds apart, and you'll see they increment too quickly to feasibly be in jiffies. The numbers are actually in nanoseconds on modern kernels, so divide by 1000000000 to convert to seconds.


-2

Using a smilar VM settings with OpenStack and this works (running Debian): sync && sudo sh -c "echo 3 > /proc/sys/vm/drop_caches"


1

These files are presented as symlinks. They point to a pseudo-file belonging to the pseudo-filesystem nsfs. Not including specialized namespace operations (done with clone(2), setns(2), unshare(2), ioctl_ns(2) etc.), the only allowed operations I know of on those files are to open (and close) them, to have a reference when manipulating namespages, or to ...


2

This is the kernel using an existing abstraction to represent a new type of thing. The files don't really "point" to anything, in the traditional symlink sense. The values are effectively handles to namespaces. The kernel uses the information internally to look up the appropriate namespace in their internal data structures. You'll see a similar type of ...


4

Since version 4.12 of the kernel, on x86 CPUs with support for the APERF / MPERF MSRs, there’s a slight delay when opening /proc/cpuinfo to ensure that the CPU frequencies are accurately reported (or at least, don’t show values which are too stale). This was changed slightly in cpufreq: x86: Make scaling_cur_freq behave more as expected (4.13, with increased ...


Top 50 recent answers are included