From: Sylvain <autofr@gmail.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: distinguish kernel thread / user task
Date: Fri, 3 Dec 2004 22:32:31 +0100 [thread overview]
Message-ID: <64b1faec0412031332573712e9@mail.gmail.com> (raw)
In-Reply-To: <41B0D18B.3020309@didntduck.org>
kernel threads have no mm struct, right.
but it appears some programs (user tasks) haven't either ?! actually,
that what I notice..
Sylvain
On Fri, 03 Dec 2004 15:50:19 -0500, Brian Gerst <bgerst@didntduck.org> wrote:
> Sylvain wrote:
> > I am trying to do a tool to record task switching...separating also
> > kernel/user tasks, but I got some trouble with that last case.
> >
> > I confused since "ps" is actually able to distinguish kernel thread
> > from user task.
> > I wouldn't had a flag if It 's not necessary
> >
> > Sylvain
> >
>
> Pstools doesn't really know the difference between user and kernel
> threads. It only shows kernel threads as swapped out (in brackets)
> because they have an RSS of zero (since kernel threads have no mm struct).
>
> --
> Brian Gerst
>
prev parent reply other threads:[~2004-12-03 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 17:16 distinguish kernel thread / user task Sylvain
2004-12-03 19:24 ` Brian Gerst
2004-12-03 20:15 ` Sylvain
2004-12-03 20:50 ` Brian Gerst
2004-12-03 21:32 ` Sylvain [this message]
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=64b1faec0412031332573712e9@mail.gmail.com \
--to=autofr@gmail.com \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.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