From: Matt Helsley <matthltc@us.ibm.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
Jean-Pierre Dion <jean-pierre.dion@bull.net>,
Jesse Barnes <jbarnes@engr.sgi.com>,
Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
Badari Pulavarty <pbadari@us.ibm.com>,
Ram Pai <linuxram@us.ibm.com>,
CKRM-Tech <ckrm-tech@lists.sourceforge.net>,
Erich Focht <efocht@hpce.nec.com>,
elsa-devel <elsa-devel@lists.sourceforge.net>,
Gerrit Huizenga <gh@us.ibm.com>, Adrian Bunk <bunk@stusta.de>,
"Chandra S. Seetharaman" <sekharan@us.ibm.com>
Subject: Re: [ckrm-tech] Re: [PATCH 00/02] Process Events Connector
Date: Tue, 25 Oct 2005 19:13:22 -0700 [thread overview]
Message-ID: <1130292802.10680.283.camel@stark> (raw)
In-Reply-To: <20051026014852.GE5856@shell0.pdx.osdl.net>
On Tue, 2005-10-25 at 18:48 -0700, Chris Wright wrote:
> * Matt Helsley (matthltc@us.ibm.com) wrote:
> > It seems to me that this is the consensus here and on LSE-Tech.
> > This patch addresses the needs of ELSA and CKRM and is amenable to using
> > the patches recently proposed on lse-tech to pull out the common piece.
>
> Sounds good. What about the SGI needs (for PAGG)? They just posted
> pnotify pretty recently. Or is that what you mean by consensus and
> possible use of 'task notifiers'?
>
> thanks,
> -chris
If this patch used pnotify it would be much more complicated and it
would need to attach small pieces of data to each task. However there
have been some alternative proposals. The 'task_notifier' patch posted
by Jack Steiner was much closer to what this patch needs:
http://marc.theaimsgroup.com/?l=lse-tech&m=112869558116290&w=2
'task_notifier' is smaller and easier to review but still requires
per-task data that would complicate the Process Events Connector patch.
There has been some discussion in the above thread on how to address the
per-task data/notification needs of PAGG and the all-task notification
needs of ELSA and CKRM.
Cheers,
-Matt Helsley
next prev parent reply other threads:[~2005-10-26 2:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 0:07 [PATCH 00/02] Process Events Connector Matt Helsley
2005-10-26 0:09 ` Matt Helsley
2005-10-26 0:12 ` [PATCH 02/02] " Matt Helsley
2005-10-26 19:30 ` Andrew Morton
2005-10-26 23:06 ` Matt Helsley
2005-10-26 0:16 ` [PATCH 01/02] Export Connector Symbol Matt Helsley
2005-10-26 6:57 ` Evgeniy Polyakov
2005-10-26 0:34 ` [PATCH 00/02] Process Events Connector Greg KH
2005-10-26 1:00 ` Matt Helsley
2005-10-26 1:16 ` Chandra Seetharaman
2005-10-26 1:22 ` Chris Wright
2005-10-26 1:30 ` [ckrm-tech] " Matt Helsley
2005-10-26 1:48 ` Chris Wright
2005-10-26 2:13 ` Matt Helsley [this message]
2005-10-26 18:34 ` Jay Lan
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=1130292802.10680.283.camel@stark \
--to=matthltc@us.ibm.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=chrisw@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=efocht@hpce.nec.com \
--cc=elsa-devel@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=greg@kroah.com \
--cc=guillaume.thouvenin@bull.net \
--cc=jbarnes@engr.sgi.com \
--cc=jean-pierre.dion@bull.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=sekharan@us.ibm.com \
/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