All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jan Beulich <jbeulich@novell.com>,
	linux-kernel@vger.kernel.org, pagg@oss.sgi.com, erikj@sgi.com,
	matthltc@us.ibm.com, pj@sgi.com
Subject: Re: [PATCH 0/4] add task handling notifier
Date: Tue, 25 Dec 2007 14:05:26 -0800	[thread overview]
Message-ID: <20071225140526.547a882f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071223122621.GA19310@infradead.org>

On Sun, 23 Dec 2007 12:26:21 +0000 Christoph Hellwig <hch@infradead.org> wrote:

> On Thu, Dec 20, 2007 at 01:11:24PM +0000, Jan Beulich wrote:
> > With more and more sub-systems/sub-components leaving their footprint
> > in task handling functions, it seems reasonable to add notifiers that
> > these components can use instead of having them all patch themselves
> > directly into core files.
> 
> I agree that we probably want something like this.  As do some others,
> so we already had a few a few attempts at similar things.  The first one
> is from SGI and called PAGG (http://oss.sgi.com/projects/pagg/) and also
> includes allocating per-task data for it's users.  Then also from SGI
> there has been a simplified version called pnotify that's also available
> from the website above.
> 
> Later Matt Helsley had something called "Task Watchers" which lwn has
> an article on: http://lwn.net/Articles/208117/.
> 
> For some reason neither ever made a lot of progess (performance
> problems?).
> 

I had it in -mm, sorted out all the problems but ended up not pulling the
trigger.

Problem is, it adds runtime overhead purely for the convenience of kernel
programmers, and I don't think that's a good tradeoff.

Sprinkling direct calls into a few well-known sites won't kill us, and
we've survived this long.  Why not keep doing that, and save everyone a few
cycles?



  reply	other threads:[~2007-12-25 22:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 13:11 [PATCH 0/4] add task handling notifier Jan Beulich
2007-12-20 22:25 ` Ingo Oeser
2007-12-21  7:36   ` Jan Beulich
2007-12-23 12:26 ` Christoph Hellwig
2007-12-25 22:05   ` Andrew Morton [this message]
2008-01-08 13:38     ` Jan Beulich
2008-01-08 22:14       ` Andrew Morton
2008-01-09  0:03         ` Paul Jackson
2008-01-09  0:31           ` Andrew Morton
2008-01-09  2:47         ` Matt Helsley
2008-01-09  3:22           ` Andrew Morton
2008-01-09  9:52         ` Jan Beulich
2008-01-09 10:03           ` Christoph Hellwig
2008-01-09  2:24   ` Matt Helsley
2008-01-09  3:27     ` Matthew Helsley

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=20071225140526.547a882f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=erikj@sgi.com \
    --cc=hch@infradead.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=pagg@oss.sgi.com \
    --cc=pj@sgi.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 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.