Re: [Lse-tech] Re: [PATCH] cpusets - big numa cpu and memory placement

Matthew Dobson
2004-10-11T22:18:45Z

On Sat, 2004-10-09 at 13:08, Paul Jackson wrote:
> Matthew, responding to Paul:
> > > If for whatever reason, you don't think it is worth the effort to morph
> > > the virtual resouce manager that is currently embedded within CKRM into
> > > an independent, neutral framework, then don't expect the rest of us to
> > > embrace it. Do you think Reiser would have gladly used vfs to plug in
> > > his file system if it had been called "ext"? In my personal opinion, it
> > > would be foolhardy for SGI, NEC, Bull, Platform (LSF) or Altair (PBS) to
> > > rely on critical technology so clearly biased toward and dominated by a
> > > natural competitor.
> >
> > I don't think that is terribly fair. I can honestly say that I'm not
> > opposing your implementation because of who you work for.
>
> Good point. I was painting with too wide a brush (hmmm ... someday I
> should see if I can get through an entire post without an analogy ...)

Doubtful. I've read too many of your posts to think that it's very
likely! ;)

> My suggestion to separate the virtual resource management framework
> (which I named 'vrm') from CKRM's other elements, such as fair share
> scheduling, was an attempt to establish such a minimum verifiable
> deliverable. That suggestion was clearly dead on arrival.

My (completely uninformed) guess is that the CKRM folks thought it would
be extremely unlikely to be able to get the 'vrm' into the kernel
without something to use it. Linus, and the rest of the community, has
been understandably reluctant to pick up large chunks of code on the
assurance that "someone, someday will use these hooks". The fair share
scheduler is thus both a proof of concept that the 'vrm' works and a
user of the 'vrm'. The 'vrm' and the fair share scheduler, should be
logically separate pieces of code, though. I should *really* read
through the CKRM code before I continue any further as I am purely
speculating now...

> My apologies for implicating everyone whose email ends in "ibm.com" in
> my earlier comment. IBM is a big place, and all manner and variety
> of people work there. It's a pleasure working with yourself, Matthew,
> and many others from IBM.

Apology accepted, Paul. IBM is a large company, and this thread in
particular has had many @ibm.com posters. It can seem there is some
large IBM conspiracy to block your efforts, but I can assure you that
isn't the case. Unless the small, painless chips on the backs of our
necks are working far better than I think they do.... :)

-Matt