public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Cc: Paul Menage <menage@google.com>,
	containers@lists.linux-foundation.org,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	dhaval@linux.vnet.ibm.com, skumar@linux.vnet.ibm.com
Subject: Re: [PATCH] sched: cpu accounting controller
Date: Thu, 29 Nov 2007 20:20:58 +0100	[thread overview]
Message-ID: <20071129192058.GC5238@elte.hu> (raw)
In-Reply-To: <20071129191737.GH5681@linux.vnet.ibm.com>


* Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:

> Paul,
> 	Sorry about the delay in getting back to this thread. I realized
> very recently that cpuacct controller has been removed from Linus's tree
> and have attempted to rework it as per our discussions.
> 
> Linus/Ingo,
> 	Commit cfb5285660aad4931b2ebbfa902ea48a37dfffa1 removed a 
> usefull feature for us, which provided a cpu accounting resource 
> controller. This feature would be usefull if someone wants to group 
> tasks only for accounting purpose and doesnt really want to exercise 
> any control over their cpu consumption.

ok, this looks certainly doable for v2.6.24. I've added it to the 
scheduler fixes queue and will let it brew there for a few days and send 
it to Linus after that if everything goes fine - unless anyone objects. 
This is pre-existing, tested code so the risk is small.

	Ingo

  reply	other threads:[~2007-11-29 19:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13  5:25 Revert for cgroups CPU accounting subsystem patch Paul Menage
2007-11-13  6:00 ` Srivatsa Vaddagiri
2007-11-13  6:05   ` Paul Menage
2007-11-13  7:00     ` Balbir Singh
2007-11-13  7:10       ` Paul Menage
2007-11-13  7:29         ` Balbir Singh
2007-11-13  7:34           ` Paul Menage
2007-11-13  7:59           ` Srivatsa Vaddagiri
2007-11-13  7:59             ` Paul Menage
2007-11-13  7:48     ` Srivatsa Vaddagiri
2007-11-13  7:57       ` Paul Menage
2007-11-29 19:17         ` [PATCH] sched: cpu accounting controller Srivatsa Vaddagiri
2007-11-29 19:20           ` Ingo Molnar [this message]
2007-11-29 19:39             ` Srivatsa Vaddagiri
2007-11-29 19:30           ` Andrew Morton
2007-11-29 20:18             ` Srivatsa Vaddagiri
2007-11-30 12:42               ` [PATCH] sched: cpu accounting controller (V2) Srivatsa Vaddagiri
2007-11-30 12:35                 ` Ingo Molnar
2007-11-30 13:09                   ` Srivatsa Vaddagiri
2007-11-30 13:34                     ` Ingo Molnar
2007-11-30 12:45                 ` Balbir Singh
2007-11-30 13:53                   ` Ingo Molnar
2007-11-30 14:00                     ` Balbir Singh
2007-11-30 18:45                     ` Balbir Singh
2007-11-30 19:46                       ` Ingo Molnar
2007-12-01  7:48                 ` Paul Menage
2007-12-01  9:51                   ` Balbir Singh

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=20071129192058.GC5238@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=skumar@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vatsa@linux.vnet.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