Re: [RFC] cpuset: add interface to isolated cpus

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


> > So ... where should it be done?
> sched.c I suppose.

Are we discussing where the implementing code should go,
or where the isolated cpu map special file should be
exposed to user space?

And you didn't answer my other questions, such as:
 1) If your other patch to manipulate sched domains
    has code that belongs in kernel/cpuset.c, and
    special files that belong in /dev/cpuset, why
    shouldn't this one naturally go in the same places?
 2) Why ... why?  What would be better about sched.c
    and what's wrong with where it is (the code and
    the exposed file)?

                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <[email protected]> 1.925.600.0401
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at
Please read the FAQ at

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux