public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Process events: Fix biarch compatibility
Date: Fri, 07 Jul 2006 16:16:00 -0700	[thread overview]
Message-ID: <1152314160.21787.2234.camel@stark> (raw)
In-Reply-To: <20060707160000.45b9a9f0.akpm@osdl.org>

On Fri, 2006-07-07 at 16:00 -0700, Andrew Morton wrote:
> Matt Helsley <matthltc@us.ibm.com> wrote:
> >
> > Andrew, I'd like to revise my request and shoot for eventual inclusion
> > in 2.6.18 if it's not too much to ask. What do you think?
> 
> I'm not sure what you're referring to here.

	I'm referring only to the biarch compatability fix for process events.
It happens to tangle with but is not dependent upon task watchers. So
it's not really in the list below.

> The per-task-delay-accounting patches I'd like to get into 2.6.18, yes. 
> We've been dicking around for *years* with enhanced system accounting
> requirements and we now seem to have a roughly-agreed-upon way of doing
> that.  I think we just need to get it in there and get people using it for
> their various accounting needs.  I was planning on getting all this into
> -rc1 but then we got derailed by the 1000-cpus-doing-1000-exits-per-second
> problem.
> 
> The task-watchers patches I really like - it fixes the problem of more and
> more subsystems adding their little own little hooks all into the same
> places.  But I think it's much less urgent than per-task-delay-accounting
> and, given that (afaik) we haven't yet resolved whether task-watchers will
> use a single notifier chain or one per event, I'm inclined to hold that
> back until 2.6.19.

	Sorry for the confusion.

Cheers,
	-Matt Helsley


      reply	other threads:[~2006-07-07 23:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 21:38 Process events: Fix biarch compatibility Matt Helsley
2006-07-07 23:00 ` Andrew Morton
2006-07-07 23:16   ` Matt Helsley [this message]

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=1152314160.21787.2234.camel@stark \
    --to=matthltc@us.ibm.com \
    --cc=akpm@osdl.org \
    --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