Re: cpuset and affinity implementation
- From: Alfred Perlstein <alfred@xxxxxxxxxxx>
- Date: Mon, 25 Feb 2008 15:17:47 -0800
* Jeff Roberson <jroberson@xxxxxxxxxxxxxx> [080224 02:39] wrote:
Please see:
http://people.freebsd.org/~jeff/cpuset.diff
This is unfortunately intertwined with ULE's new CPU selection algorithm
so that code is in the patch as well. Otherwise, this includes a simple,
ugly userland tool called cpuset and all of the kernel support required.
I have tested this by creating sets and subsets and modifying their cpu
masks under load. I'm able to dynamically reprovision without issue.
This doesn't have support for jails but the infrastructure is there. It
also fails to modify sets if it would leave threads without a valid cpu
to run on. I have not implemented a force option but it will be trivial
to do so. The initial cpu set is also created before we know all_cpus so
it's faked up with all cpus set for now.
I mostly want people to look at the interface in cpuset.h and make sure
they agree with it before I start polishing to commit. I'm fairly happy
with the way the syscall api looks now. The code itself ended up being
much more complicated than I'd hoped due to locking considerations. Try
not to look at cpuset_setproc() ;).
Jeff, this is very cool. I do have one issue though:
+ * A thread may not be assigned to a a group seperate from other threads in
+ * the process. This is to remove ambiguity when the setid is queried with
+ * a pid argument. There is no other technical limitation.
Am I understanding things correctly such that within a process there
can only be one "set"?
If so this restricts some of the benifits you get with sets and
binding.
An example would be some sort of system with multiple CPUs where some
are assigned specifically for pseudo-realtime processing and others are for
general control things such as cli, stats, etc.
In our case we would like to be able to run some threads on specific
cpu sets, and other threads to be run anywhere on the control CPUs.
Can this be done with this API?
-Alfred
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: cpuset and affinity implementation
- From: Jeff Roberson
- Re: cpuset and affinity implementation
- References:
- Re: Linux compatible setaffinity.
- From: Jeff Roberson
- getaffinity/setaffinity and cpu sets.
- From: Jeff Roberson
- Re: getaffinity/setaffinity and cpu sets.
- From: Robert Watson
- Re: getaffinity/setaffinity and cpu sets.
- From: Jeff Roberson
- Re: getaffinity/setaffinity and cpu sets.
- From: Brooks Davis
- Re: getaffinity/setaffinity and cpu sets.
- From: Jeff Roberson
- Re: getaffinity/setaffinity and cpu sets.
- From: Brooks Davis
- Re: getaffinity/setaffinity and cpu sets.
- From: Jeff Roberson
- Re: getaffinity/setaffinity and cpu sets.
- From: Brooks Davis
- cpuset and affinity implementation
- From: Jeff Roberson
- Re: Linux compatible setaffinity.
- Prev by Date: cpuset and affinity implementation
- Next by Date: Re: cpuset and affinity implementation
- Previous by thread: cpuset and affinity implementation
- Next by thread: Re: cpuset and affinity implementation
- Index(es):