Title says it all.
Here's a proposal for a sysctl(7) knob to easily allow non-superusers to
set the CPU affinity of processes and threads they own:
security.secmodel.suser.usersetaffinity
(ressembles the one already existing to allow for user mounts)
Would it be acceptable to modify current
Hello Lars,
Sorry for late reply.
Lars Heidieker l...@heidieker.de wrote:
i uploaded a new version of the kmem-pool-vmem-uvm patch:
ftp://ftp.netbsd.org/pub/NetBSD/misc/para/kmem-pool-vmem-uvm.patch
...
I've uploaded a new Version of the patch and a small patch that
replaces malloc
At Tue, 01 Nov 2011 01:43:23 -0700, Greg A. Woods wo...@planix.ca wrote:
Subject: Re: getrusage() problems with user vs. system time reporting
Indeed with all this doom and gloom about TSC it seems it might be
better just to use binuptime() -- that probably won't be as fast
though
On Wed, Nov 02, 2011 at 06:23:40PM -0700, Greg A. Woods wrote:
Unfortunately getbinuptime() isn't immediately looking a whole lot
better than the statistical sampling in statclock(), though perhaps,
with enough benchmark runtime, it is, as expected, being _much_ more
fair at splitting between
On Thu, 03 Nov 2011 01:50:49 +0100
Jean-Yves Migeon j...@netbsd.org wrote:
Here's a proposal for a sysctl(7) knob to easily allow non-superusers to
set the CPU affinity of processes and threads they own:
security.secmodel.suser.usersetaffinity
(ressembles the one already existing to
