[lkml]   [2004]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Lse-tech] [RFC PATCH] scheduler: Dynamic sched_domains
On Sun, 2004-10-10 at 05:45, Erich Focht wrote:
> On Saturday 09 October 2004 03:05, Matthew Dobson wrote:
> > I personally like to think of it from the top down. The internal API I
> > came up with looks like:
> >
> > create_domain(parent_domain, type);
> > destroy_domain(domain);
> > add_cpu_to_domain(cpu, domain);
> I'd suggest adding:
> reparent_domain(domain, new_parent_domain);
> When I said that the domains tree is standing on its leaves I meant
> that the core components are the CPUs. Or the Nodes, if you already
> have them. Or some supernodes, if you already have them. In a "normal"
> filesystem you have the root directory, create subdirectories and
> create files in them. Here you already have the files but not the
> structure (or the simplest possible structure).
> Anyhow, the 4 command API can well be the guts of the directory
> operations API which I proposed.
> Regards,
> Erich

I like that suggestion. As Paul has been sucked away to other work,
thus giving me a chance to work on my code. I will be focusing on
getting the cpusets/CKRM style interface working with my sched_domains
API. I like the reparent_domain() suggestion, and it makes sense with
the 'mv' command, in regards to the filesystem model that cpusets/CKRM
currently uses.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:06    [W:0.098 / U:10.140 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site