Re: broadcast oddity

Wed, Jul 20, 2011 at 12:34:38PM +0300, Daniel Braniss wrote: from the diskless: els-01# ifconfig vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8280bRXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE ether 00:0d:b9:22:57:18 inet

Autosizing column widths in ps(1).

Patch below changes ps(1) to automatically size column widths according to their contents. From the user point of view, it prevents breaking layout with too wide values and in most cases makes output narrower. From the developer point of view, it removes the need to specify widths. Testing is

Re: Autosizing column widths in ps(1).

Edward Tomasz Napierała tr...@freebsd.org writes: Patch below changes ps(1) to automatically size column widths according to their contents. From the user point of view, it prevents breaking layout with too wide values and in most cases makes output narrower. From the developer point of

Silicon Image programming docs

Found some datasheets (programming docs) and board schematics for Silicon Image storage controllers. Since they don't seem to be publicly available, perhaps some of these docs will be useful. Bcc'd relevant fs and hackers lists. Reply to hardware I guess. # Overview

UMA large allocations issues

Hi. I'm a student and some time ago I started investigating a bit about the performance/fragmentation issue of large allocations within the UMA allocator. Benckmarks showed up that this problems of performances are mainly related to the fact that every call to uma_large_malloc() results in a call

DTrace script asserts and kills the other process

I am trying to run this dtrace script: #!/usr/sbin/dtrace -s pid123:libc::entry { self-timestmp[probefunc] = timestmp; } pid123:libc::return /self-timestmp[probefunc] != 0/ { @function_duration[probefunc] = sum(timestmp - self-timestmp[probefunc]); timestmp[probefunc] = 0; } which I got from