Re: [htop-general] Preparing for 1.0
Brought to you by:
loderunner
|
From: Hisham <his...@gm...> - 2011-11-18 14:17:42
|
On Fri, Nov 18, 2011 at 5:48 AM, Eugene V. Lyubimkin <ja...@de...> wrote: > Hello Hisham, > > On 2011-11-18 04:19, Hisham wrote: >> I just made a major commit to SVN, containing the latest features and >> tweaks in preparation for htop 1.0. > > Nice to hear. > >> [...] and tries to use the native Linux sched_setaffinity function >> instead of the hwloc library. My plan is to remove the embedded hwloc >> library from the sources. My recommendation for distro packagers is to >> use the native affinity support. It should work with all modern >> kernels/glibc's out there, and it makes htop noticeably lighter. > > Hm, what about non-Linux ports, namely, FreeBSD? I only officially support Linux and never tested htop on FreeBSD myself -- having said that, users reported success with it by using the a Linux-compatible procfs on FreeBSD, and some suggested minor changes to htop which I was happy to apply. I don't know if affinity controls even work today on FreeBSD. Even on PLPA/hwloc, the calls were Linux-specific AFAIK. I've been keeping CPU affinity as an optional feature, and yes, from a quick Google search, it looks lke CPU affinity is disabled on FreeBSD. hwloc is only there to cater for very old incompatible kernel/glibc interfaces, but for now I still plan to keep it around as an optional feature. I added proper tests for the native sched_setaffinity API in the configure script, so, if --enable-native-affinity --disable-hwloc builds and runs in the system, you're not losing anything by going with that (and you get a smaller binary with less disk and memory footprint). -- Hisham |