All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc@us.ibm.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Andrew Morton <akpm@osdl.org>,
	Shailabh Nagar <nagar@watson.ibm.com>,
	"Chandra S. Seetharaman" <sekharan@us.ibm.com>,
	"John T. Kohl" <jtk@us.ibm.com>, Balbir Singh <balbir@in.ibm.com>,
	Jes Sorensen <jes@sgi.com>, LKML <linux-kernel@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	LSE <lse-tech@lists.sourceforge.net>
Subject: Re: [Lse-tech] [PATCH 00/11] Task watchers:  Introduction
Date: Wed, 21 Jun 2006 14:32:10 -0700	[thread overview]
Message-ID: <1150925530.21787.1060.camel@stark> (raw)
In-Reply-To: <4499222A.5090403@bigpond.net.au>

On Wed, 2006-06-21 at 20:40 +1000, Peter Williams wrote:
> Matt Helsley wrote:
> > On Wed, 2006-06-21 at 02:07 -0700, Andrew Morton wrote:
> >> On Wed, 21 Jun 2006 01:35:29 -0700
> >> Matt Helsley <matthltc@us.ibm.com> wrote:

<snip>

> >>> Alternately,
> >>> I could produce patches that apply on top of the current set.
> >> It depends on how many of the existing patches are affected.  If it's just
> >> one or two then an increment would be fine.  If it's everything then a new
> >> patchset I guess.
> > 
> > It would affect most of them -- I'd need to change the bits that
> > register a notifier block. So I'll make a separate series.
> 
> How about making WATCH_TASK_INIT and friends flags so that clients can 
> then pass a mask (probably part of the notifier_block) that specifies 
> which ones they wish to be notified of.  This would save unnecessary 
> function calls.
> 
> Peter

	Yes, I was considering that. However, I realized that it still would
involve either multiple notifier blocks or significant, non-intuitive
changes in the notifier chain code so that one notifier block could be
registered on multiple chains.

	I'll keep this suggestion in mind.

Cheers,
	-Matt Helsley


  reply	other threads:[~2006-06-21 21:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13 23:52 [PATCH 00/11] Task watchers: Introduction Matt Helsley
2006-06-19 10:24 ` Andrew Morton
2006-06-21  8:35   ` Matt Helsley
2006-06-21  9:07     ` Andrew Morton
2006-06-21  9:13       ` [Lse-tech] " Matt Helsley
2006-06-21 10:40         ` Peter Williams
2006-06-21 21:32           ` Matt Helsley [this message]
2006-06-21  5:41 ` Peter Williams
2006-06-21  7:51   ` Matt Helsley
2006-06-21 11:34     ` Peter Williams
2006-06-21 11:41       ` Peter Williams
2006-06-21 21:29         ` Matt Helsley
2006-06-21 23:04           ` Peter Williams
2006-06-22  0:32             ` Matt Helsley
2006-06-22  1:11               ` Peter Williams
2006-06-22  3:46                 ` Matt Helsley
2006-06-22  4:26                   ` Peter Williams
2006-06-22  5:37                     ` [Lse-tech] " Matt Helsley
2006-06-22  6:29                       ` Peter Williams
2006-06-22 19:53                         ` Chandra Seetharaman
2006-06-22 22:46                           ` Peter Williams

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=1150925530.21787.1060.camel@stark \
    --to=matthltc@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=balbir@in.ibm.com \
    --cc=jes@sgi.com \
    --cc=jtk@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=nagar@watson.ibm.com \
    --cc=pwil3058@bigpond.net.au \
    --cc=sekharan@us.ibm.com \
    --cc=stern@rowland.harvard.edu \
    /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.