From: mueddib@yandex.com (Ozgur Karatas)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel CPU Utilization
Date: Fri, 21 Apr 2017 20:04:05 +0300 [thread overview]
Message-ID: <4605311492794245@web6o.yandex.ru> (raw)
In-Reply-To: <20170421161757.GA14406@pride.cult>
21.04.2017, 19:19, "Stephen Brennan" <stephen@brennan.io>:
> Hello all,
Hello,
> I was wondering if anyone had some information on how CPU time used by the
> kernel is accounted for, e.g. in top or htop. I would imagine that kernel code
> running in process code would be "billed" toward that process. What about kernel
> worker threads (for example, work_structs queued for later)?
>
> My overall goal is that I'm doing some large-scale network emulation, and I want
> to ensure that the kernel is not using too much CPU time, otherwise the CPU
> overhead may be messing with the results.
I written to the code for myself, you can use and develop this code (open source).
https://github.com/mueddib/cpustat
> Thanks,
> Stephen
Regards,
Ozgur
next prev parent reply other threads:[~2017-04-21 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 16:17 Kernel CPU Utilization Stephen Brennan
2017-04-21 17:04 ` Ozgur Karatas [this message]
2017-04-21 17:09 ` Ozgur Karatas
2017-04-25 8:58 ` Mulyadi Santosa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4605311492794245@web6o.yandex.ru \
--to=mueddib@yandex.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).