From: Paul Jackson <pj@sgi.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: sekharan@us.ibm.com, jtk@us.ibm.com, jes@sgi.com,
linux-kernel@vger.kernel.org, linux-audit@redhat.com,
viro@zeniv.linux.org.uk, lse-tech@lists.sourceforge.net,
menage@google.com, sgrubb@redhat.com, hch@lst.de
Subject: Re: [RFC][PATCH 00/10] Task watchers v2 Introduction
Date: Thu, 28 Sep 2006 19:41:42 -0700 [thread overview]
Message-ID: <20060928194142.cece62bb.pj@sgi.com> (raw)
In-Reply-To: <20060929020232.756637000@us.ibm.com>
How might this play with Paul Menage's <menage@google.com> patch posted
earlier today on lkml:
[RFC][PATCH 0/4] Generic container system
My cpuset_exit() call is getting popular - both you guys seem to have
designs on it.
Separate question - I guess that your task watcher mechanism, the
way it uses linker magic now, would not enable a loadable module
to plug into these various fork/exit/... hooks. Is that right?
Such an ability for loadable modules to get callouts on fork/exit
would be useful to some ... it could also be a controversial ability.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, jes@sgi.com,
lse-tech@lists.sourceforge.net, sekharan@us.ibm.com,
jtk@us.ibm.com, hch@lst.de, viro@zeniv.linux.org.uk,
sgrubb@redhat.com, linux-audit@redhat.com, menage@google.com
Subject: Re: [RFC][PATCH 00/10] Task watchers v2 Introduction
Date: Thu, 28 Sep 2006 19:41:42 -0700 [thread overview]
Message-ID: <20060928194142.cece62bb.pj@sgi.com> (raw)
In-Reply-To: <20060929020232.756637000@us.ibm.com>
How might this play with Paul Menage's <menage@google.com> patch posted
earlier today on lkml:
[RFC][PATCH 0/4] Generic container system
My cpuset_exit() call is getting popular - both you guys seem to have
designs on it.
Separate question - I guess that your task watcher mechanism, the
way it uses linker magic now, would not enable a loadable module
to plug into these various fork/exit/... hooks. Is that right?
Such an ability for loadable modules to get callouts on fork/exit
would be useful to some ... it could also be a controversial ability.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-09-29 2:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 2:02 [RFC][PATCH 00/10] Task watchers v2 Introduction Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:02 ` [RFC][PATCH 01/10] Task watchers v2 Task watchers v2 Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:02 ` [RFC][PATCH 02/10] Task watchers v2 Benchmark Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:32 ` Paul Jackson
2006-09-29 2:32 ` [Lse-tech] " Paul Jackson
2006-09-29 19:38 ` Matt Helsley
2006-09-29 20:13 ` Paul Jackson
2006-09-29 20:13 ` [Lse-tech] " Paul Jackson
2006-09-30 0:01 ` Matt Helsley
2006-09-30 0:01 ` [Lse-tech] " Matt Helsley
2006-09-30 0:04 ` Paul Jackson
2006-09-30 0:04 ` [Lse-tech] " Paul Jackson
2006-09-29 2:02 ` [RFC][PATCH 03/10] Task watchers v2 Register audit task watcher Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:02 ` [RFC][PATCH 04/10] Task watchers v2 Register semundo " Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:02 ` [RFC][PATCH 05/10] Task watchers v2 Register cpuset " Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:31 ` Paul Jackson
2006-09-29 2:31 ` Paul Jackson
2006-09-29 7:52 ` [Lse-tech] " Matt Helsley
2006-09-29 8:03 ` Paul Jackson
2006-09-29 8:03 ` [Lse-tech] " Paul Jackson
2006-09-29 2:02 ` [RFC][PATCH 06/10] Task watchers v2 Register NUMA mempolicy " Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:02 ` [RFC][PATCH 07/10] Task watchers v2 Register IRQ flag tracing " Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:02 ` [RFC][PATCH 08/10] Task watchers v2 Register lockdep " Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:02 ` [RFC][PATCH 09/10] Task watchers v2 Register process keyrings " Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:02 ` [RFC][PATCH 10/10] Task watchers v2 Register process events connector Matt Helsley
2006-09-29 2:02 ` Matt Helsley
2006-09-29 2:41 ` Paul Jackson [this message]
2006-09-29 2:41 ` [RFC][PATCH 00/10] Task watchers v2 Introduction Paul Jackson
2006-09-29 8:16 ` [RFC][PATCH] Task watchers and modules (WAS Re: [RFC][PATCH 00/10] Task watchers v2 Introduction) Matt Helsley
2006-09-29 16:22 ` [RFC][PATCH 00/10] Task watchers v2 Introduction Paul Menage
2006-09-29 16:22 ` Paul Menage
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=20060928194142.cece62bb.pj@sgi.com \
--to=pj@sgi.com \
--cc=hch@lst.de \
--cc=jes@sgi.com \
--cc=jtk@us.ibm.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=matthltc@us.ibm.com \
--cc=menage@google.com \
--cc=sekharan@us.ibm.com \
--cc=sgrubb@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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 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.