From: "Leonidas ." <leonidas137@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Notification when a task is created/exits
Date: Wed, 17 Feb 2010 08:46:51 +0530 [thread overview]
Message-ID: <f22d86811002161916s292436b7hf564269a37dbe9af@mail.gmail.com> (raw)
In-Reply-To: <20100217115313.30de11fb.kamezawa.hiroyu@jp.fujitsu.com>
Hi Kame,
>
> 1. use NETLINK and catch task create/exit in userland.
> But this means "catch" is asyncronous.
>
This does not sounds like a possible solution to me in my setup. Using netlink
and having an user space component to do this job might be an over kill in what
I am doing.
> 2. implement cgroup subsystem
> AFAIK, in the latest kernel, cgroup subsystem can be implemented as module.
> cgroup has fork/exit handler.
> And you can implement some useful controls for tasks you watch via
> cgroup's control interface.
>
This sounds close to what I have in mind, but unfortunately I dont
have any idea what is cgroup
subsystem. How to implement cgroup subsystem? Can you give pointers to
some existing code
or document? Also, using this mechanism can we monitor each thread created in
user space? I.e. it is only a fork handler or even a
pthread_create/clone can be tracked this way.
> Thanks,
> -Kame
>
>
>> -Leo.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
>
--
-Leo.
next prev parent reply other threads:[~2010-02-17 3:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 5:48 Notification when a task is created/exits Leonidas .
2010-02-17 2:53 ` KAMEZAWA Hiroyuki
2010-02-17 3:16 ` Leonidas . [this message]
2010-02-17 3:43 ` KAMEZAWA Hiroyuki
2010-02-17 5:43 ` Leonidas .
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=f22d86811002161916s292436b7hf564269a37dbe9af@mail.gmail.com \
--to=leonidas137@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).