* Kernel threads and system usage metric.
@ 2012-03-09 11:39 Daniel Hilst
2012-03-09 18:25 ` Mulyadi Santosa
0 siblings, 1 reply; 4+ messages in thread
From: Daniel Hilst @ 2012-03-09 11:39 UTC (permalink / raw)
To: kernelnewbies
Doubt!
The processes that appear in top with brackets are the kernel threads?
If so, this threads spend all its time on system mode, right? By the
system mode I mean the %sy on top header, since kernel threads hasn't
any memory mapped to user space, it can't run on user space at any time,
right?
So the total of system mode usage is the sum of all processes processing
in kernel space, plus the kernel threads processing, right?
Thanks in advance!
--
Follow the white rabbit!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Kernel threads and system usage metric.
2012-03-09 11:39 Kernel threads and system usage metric Daniel Hilst
@ 2012-03-09 18:25 ` Mulyadi Santosa
2012-03-12 11:54 ` Daniel Hilst
2012-03-12 15:12 ` Chetan Nanda
0 siblings, 2 replies; 4+ messages in thread
From: Mulyadi Santosa @ 2012-03-09 18:25 UTC (permalink / raw)
To: kernelnewbies
Hi :)
On Fri, Mar 9, 2012 at 18:39, Daniel Hilst <danielhilst@gmail.com> wrote:
> The processes that appear in top with brackets are the kernel threads?
Yup :)
> If so, this threads spend all its time on system mode, right?
Yes, it supposed to ...
>By the
> system mode I mean the %sy on top header, since kernel threads hasn't
> any memory mapped to user space, it can't run on user space at any time,
> right?
IIRC, kernel thread simply "borrow" any previous scheduled task's
address space. In that matter, it also has user address space. So, if
wanted, kernel thread could access user space. But normally it doesn't
do it.
>
>
> So the total of system mode usage is the sum of all processes processing
> in kernel space, plus the kernel threads processing, right?
remember that kernel threads are also processes, so no need to
differentiate between normal processes and kernel threads, especially
when we talk about CPU utilization.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Kernel threads and system usage metric.
2012-03-09 18:25 ` Mulyadi Santosa
@ 2012-03-12 11:54 ` Daniel Hilst
2012-03-12 15:12 ` Chetan Nanda
1 sibling, 0 replies; 4+ messages in thread
From: Daniel Hilst @ 2012-03-12 11:54 UTC (permalink / raw)
To: kernelnewbies
On 03/09/2012 06:25 PM, Mulyadi Santosa wrote:
> Hi :)
>
> On Fri, Mar 9, 2012 at 18:39, Daniel Hilst<danielhilst@gmail.com> wrote:
>> The processes that appear in top with brackets are the kernel threads?
>
> Yup :)
>
>> If so, this threads spend all its time on system mode, right?
>
> Yes, it supposed to ...
>
>> By the
>> system mode I mean the %sy on top header, since kernel threads hasn't
>> any memory mapped to user space, it can't run on user space at any time,
>> right?
>
> IIRC, kernel thread simply "borrow" any previous scheduled task's
> address space. In that matter, it also has user address space. So, if
> wanted, kernel thread could access user space. But normally it doesn't
> do it.
>
>>
>>
>> So the total of system mode usage is the sum of all processes processing
>> in kernel space, plus the kernel threads processing, right?
>
> remember that kernel threads are also processes, so no need to
> differentiate between normal processes and kernel threads, especially
> when we talk about CPU utilization.
>
Thanks Mulyadi!
--
Follow the white rabbit!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Kernel threads and system usage metric.
2012-03-09 18:25 ` Mulyadi Santosa
2012-03-12 11:54 ` Daniel Hilst
@ 2012-03-12 15:12 ` Chetan Nanda
1 sibling, 0 replies; 4+ messages in thread
From: Chetan Nanda @ 2012-03-12 15:12 UTC (permalink / raw)
To: kernelnewbies
On Mar 9, 2012 11:57 PM, "Mulyadi Santosa" <mulyadi.santosa@gmail.com>
wrote:
>
> Hi :)
>
> On Fri, Mar 9, 2012 at 18:39, Daniel Hilst <danielhilst@gmail.com> wrote:
> > The processes that appear in top with brackets are the kernel threads?
>
> Yup :)
>
> > If so, this threads spend all its time on system mode, right?
>
> Yes, it supposed to ...
>
> >By the
> > system mode I mean the %sy on top header, since kernel threads hasn't
> > any memory mapped to user space, it can't run on user space at any time,
> > right?
>
> IIRC, kernel thread simply "borrow" any previous scheduled task's
> address space. In that matter, it also has user address space. So, if
> wanted, kernel thread could access user space. But normally it doesn't
> do it.
>
AFAIK kernel threads do not have any userspace context. As it is never
gaurnted which userspace process was previously running when kernel thread
scheduled to run.
> >
> >
> > So the total of system mode usage is the sum of all processes processing
> > in kernel space, plus the kernel threads processing, right?
>
> remember that kernel threads are also processes, so no need to
> differentiate between normal processes and kernel threads, especially
> when we talk about CPU utilization.
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120312/df71ca11/attachment.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-03-12 15:12 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-09 11:39 Kernel threads and system usage metric Daniel Hilst
2012-03-09 18:25 ` Mulyadi Santosa
2012-03-12 11:54 ` Daniel Hilst
2012-03-12 15:12 ` Chetan Nanda
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.