hi,
y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) wrote:
why did you change kcpuset_t to a pointer from a structure?
i always feel awkward to compare an opaque type with NULL.
The reason is that kcpuset_t now points directly to the bit field rather
than opaque struct kcpuset_impl. Do you
y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) wrote:
why did you change kcpuset_t to a pointer from a structure?
i always feel awkward to compare an opaque type with NULL.
The reason is that kcpuset_t now points directly to the bit field rather
than opaque struct kcpuset_impl. Do you
y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) wrote:
Here is a reworked dynamic CPU set implementation for kernel (shared
cpuset.c in src/common will be moved to libc) - a kcpuset(9) interface:
http://www.netbsd.org/~rmind/kcpuset_ng.diff
It supports early use while the system is cold
hi,
y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) wrote:
Here is a reworked dynamic CPU set implementation for kernel (shared
cpuset.c in src/common will be moved to libc) - a kcpuset(9) interface:
http://www.netbsd.org/~rmind/kcpuset_ng.diff
It supports early use while the system
hi,
Hello,
Here is a reworked dynamic CPU set implementation for kernel (shared
cpuset.c in src/common will be moved to libc) - a kcpuset(9) interface:
http://www.netbsd.org/~rmind/kcpuset_ng.diff
It supports early use while the system is cold through a fix up mechanism,
see
Hello,
Here is a reworked dynamic CPU set implementation for kernel (shared
cpuset.c in src/common will be moved to libc) - a kcpuset(9) interface:
http://www.netbsd.org/~rmind/kcpuset_ng.diff
It supports early use while the system is cold through a fix up mechanism,
see kcpuset_sysinit
