Re: DTrace: Sending ^C while running script produces no output

On Thu, Dec 2, 2010 at 11:48 PM, Artem Belevich wrote: > On Thu, Dec 2, 2010 at 9:46 PM, Artem Belevich wrote: >> On Thu, Dec 2, 2010 at 9:20 PM, Brandon Gooch >> wrote: >>> I've been tinkering with DTrace a bit, and I've notice something >>> peculiar on each system I've tried it on. >>> >>> Sen

MADV_FREE and vm_page_dontneed()

Is there a good reason why physical memory pages released by madvise(...,MADV_FREE) get handled by vm_page_dontneed()? vm_page_dontneed() leaves page that are already in the inactive queue where they are, and otherwise distributes pages between the active queue, and the inactive queue's tail and h

coretemp(4)/amdtemp(4) and sysctl nodes

There are very few uses in FreeBSD mainline code of sysctl_remove_oid(), and I was looking at potentially removing them. However, the use in coretemp/amdtemp has me slightly stumped. Each device provides a device_get_sysctl_ctx sysctl_ctx that is automatically cleaned up when the device goes away.

small dtrace patch for review

The patch is not about DTrace functionality, but about infrastructure use in one particular place. http://people.freebsd.org/~avg/dtrace_gethrtime_init.diff I believe that sched_pin() is need there to make sure that "host"/base CPU stays the same for all calls to smp_rendezvous_cpus(). The pc_cpum