All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: dipankar@in.ibm.com, vatsa@in.ibm.com, mingo@elte.hu,
	nickpiggin@yahoo.com.au, sam@vilain.net,
	linux-kernel@vger.kernel.org, dev@openvz.org, efault@gmx.de,
	balbir@in.ibm.com, nagar@watson.ibm.com, haveblue@us.ibm.com,
	pj@sgi.com
Subject: Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller
Date: Fri, 04 Aug 2006 12:10:35 -0700	[thread overview]
Message-ID: <1154718635.11679.11.camel@linuxchandra> (raw)
In-Reply-To: <20060803234537.e9b6736d.akpm@osdl.org>

On Thu, 2006-08-03 at 23:45 -0700, Andrew Morton wrote:
> On Fri, 4 Aug 2006 11:50:36 +0530
> Dipankar Sarma <dipankar@in.ibm.com> wrote:
> 
> > > And now we've dumped the good infrastructure and instead we've contentrated
> > > on the controller, wired up via some imaginative ab^H^Hreuse of the cpuset
> > > layer.
> > 
> > FWIW, this controller was originally written for f-series.
> 
> What the heck is an f-series?

That is how the latest posting was referred in ckrm-tech mailing list. 
> 
> <googles, looks at
> http://images.automotive.com/cob/factory_automotive/images/Features/auto_shows/2005_IEAS/2005_Ford_F-series_Harley-Davidson_front.JPG,
> gets worried about IBM design methodologies>

he he...
> 
> > It should
> > be trivial to put it back there. So really, f-series isn't gone 
> > anywhere. If you want to merge it, I am sure it can be re-submitted.
> 
> Well.  It shouldn't be a matter of what I want to merge - you're the
> resource-controller guys.  But...
> 
> > > I wonder how many of the consensus-makers were familiar with the
> > > contemporary CKRM core?
> > 
> > I think what would be nice is a clear strategy on whether we need
> > to work out the infrastructure or the controllers first.
> 
> We should put our thinking hats on and decide what sort of infrastructure
> will need to be in place by the time we have a useful number of useful
> controllers implemented.
> 
> > One of
> > the strongest points raised in the BoF was - forget the infrastructure
> > for now, get some mergable controllers developed.
> 
> I wonder what inspired that approach.  Perhaps it was a reaction to CKRM's
> long and difficult history?  Perhaps it was felt that doing standalne
> controllers with ad-hoc interfaces would make things easier to merge?
> 
> Perhaps.  But I think you guys know that the end result would be inferior,
> and that getting good infrastructure in place first will produce a better
> end result, but you decided to go this way because you want to get
> _something_ going?

To some extent yes... 
> 
> > If you
> > want to stick to f-series infrastructure and want to see some
> > consensus controllers evolve on top of it, that can be done too.
> 
> Do you think that the CKRM core as last posted had any unnecessary
> features?  I don't have the operational experience to be able to judge

No, not at all. But there were some disagreements w.r.t which interface
to use. So, as pointed by Vatsa in a different email, we wanted to
proceed with controller implementation (where we can get more
agreements) and avoid the controversial topic for now.
> that, so I'd prefer to trust your experience and judgement on that.  But
> the features which _were_ there looked quite OK from an implementation POV.
> 
> So my take was "looks good, done deal - let's go get some sane controllers
> working".  And now this!
-- 

----------------------------------------------------------------------
    Chandra Seetharaman               | Be careful what you choose....
              - sekharan@us.ibm.com   |      .......you may get it.
----------------------------------------------------------------------



  parent reply	other threads:[~2006-08-04 19:10 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  5:07 [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller Srivatsa Vaddagiri
2006-08-04  5:09 ` [ RFC, PATCH 1/5 ] CPU controller - base changes Srivatsa Vaddagiri
2006-08-04  7:35   ` Andrew Morton
2006-08-04 11:18     ` Srivatsa Vaddagiri
2006-08-04 14:34   ` Kirill Korotaev
2006-08-04 14:50     ` Balbir Singh
2006-08-04 14:51     ` Srivatsa Vaddagiri
2006-08-04  5:10 ` [ RFC, PATCH 2/5 ] CPU controller - Define group operations Srivatsa Vaddagiri
2006-08-04 23:10   ` Jiri Slaby
2006-08-04  5:11 ` [ RFC, PATCH 3/5 ] CPU controller - deal with movement of tasks Srivatsa Vaddagiri
2006-08-04  5:12 ` [ RFC, PATCH 4/5 ] CPU controller - deal with dont care groups Srivatsa Vaddagiri
2006-08-04  5:13 ` [ RFC, PATCH 5/5 ] CPU controller - interface with cpusets Srivatsa Vaddagiri
2006-08-04  5:36 ` [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller Andrew Morton
2006-08-04  5:42   ` Andrew Morton
2006-08-04  9:49     ` Alan Cox
2006-08-04 11:41       ` Srivatsa Vaddagiri
2006-08-04 14:51         ` Kirill Korotaev
2006-08-04 15:31           ` Srivatsa Vaddagiri
2006-08-04 16:03             ` Kirill Korotaev
2006-08-04 17:02               ` [ProbableSpam] " Shailabh Nagar
2006-08-04 18:27               ` Rohit Seth
2006-08-04 19:11                 ` Shailabh Nagar
2006-08-04 19:24                   ` Rohit Seth
2006-08-07  7:19                 ` Kirill Korotaev
2006-08-07 17:14                   ` Rohit Seth
2006-08-08  7:17                     ` Kirill Korotaev
2006-08-08 17:16                       ` Rohit Seth
2006-08-04 17:50           ` Martin Bligh
2006-08-07  7:25             ` Kirill Korotaev
2006-08-07 14:34               ` Martin J. Bligh
2006-08-07 16:33                 ` Kirill Korotaev
2006-08-07 18:31                   ` Rohit Seth
2006-08-07 18:43                     ` Dave Hansen
2006-08-07 19:00                       ` Rohit Seth
2006-08-07 19:46                         ` Martin Bligh
2006-08-08 14:19                           ` memory resource accounting (was Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller) Nick Piggin
2006-08-08 14:57                             ` Dave Hansen
2006-08-08 15:22                               ` Nick Piggin
2006-08-09 13:43                                 ` Kirill Korotaev
2006-08-08 17:08                             ` Martin Bligh
2006-08-09  1:54                               ` Nick Piggin
2006-08-08 17:34                             ` Rohit Seth
2006-08-09  4:33                             ` Andi Kleen
2006-08-09  6:00                               ` Magnus Damm
2006-08-09  6:06                                 ` Andi Kleen
2006-08-09  6:56                             ` Andrey Savochkin
2006-08-08  7:19                     ` [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller Kirill Korotaev
2006-08-04 16:16         ` Kirill Korotaev
2006-08-04 16:49           ` [ProbableSpam] " Shailabh Nagar
2006-08-04 17:03             ` Dipankar Sarma
2006-08-04 18:17               ` Shailabh Nagar
2006-08-07  7:23               ` Kirill Korotaev
2006-08-04 14:57       ` Kirill Korotaev
2006-08-04  5:58   ` Paul Jackson
2006-08-04  6:02   ` Paul Jackson
2006-08-04  6:16     ` Paul Jackson
2006-08-04  6:20   ` Dipankar Sarma
2006-08-04  6:31     ` Paul Jackson
2006-08-04  6:37       ` Dipankar Sarma
2006-08-04  6:49         ` Andrew Morton
2006-08-04  6:45     ` Andrew Morton
2006-08-04  7:10       ` Dipankar Sarma
2006-08-04  7:24         ` Andrew Morton
2006-08-04 19:10       ` Chandra Seetharaman [this message]
2006-08-04  6:56   ` Srivatsa Vaddagiri
2006-08-04  7:13     ` Andrew Morton
2006-08-04 11:16       ` Srivatsa Vaddagiri
2006-08-04 18:51         ` Andrew Morton
2006-08-04 14:20   ` Kirill Korotaev
2006-08-04 14:35     ` Christoph Hellwig
2006-08-04 15:29     ` [ProbableSpam] " Shailabh Nagar
2006-08-07  7:29       ` Kirill Korotaev
2006-08-07  9:30         ` Paul Jackson
2006-08-07 15:58           ` Chandra Seetharaman
2006-08-07 16:10           ` Kirill Korotaev
2006-08-07 17:15             ` Paul Jackson
2006-08-07 18:19               ` Rohit Seth
2006-08-05  3:30   ` Nick Piggin

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=1154718635.11679.11.camel@linuxchandra \
    --to=sekharan@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=balbir@in.ibm.com \
    --cc=dev@openvz.org \
    --cc=dipankar@in.ibm.com \
    --cc=efault@gmx.de \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nagar@watson.ibm.com \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pj@sgi.com \
    --cc=sam@vilain.net \
    --cc=vatsa@in.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 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.