Re: Tru64 AdvFS porting to NetBSD - 2. status 2014-10-11

[Justin Cormack <justin%specialbusservice.com@localhost>]

On Sun, Oct 12, 2014 at 11:06 AM, Kamil Rytarowski <n54%gmx.com@localhost> wrote:
> Hello,
>
>> Are you sure a new dtrace provider would not be the way to go?
>
> Yes. I believe that internal performance tracing and tracking locks is misdesign (also not very portable). I'm not familiar with DTrace, more with Linux tools (perf, valgrind) and my general plan was to debug it with librump in Linux.
>
> Of course the first milestone is not performance optimization but getting it well integrated with NetBSD and stable. That's why I took Tru64 long-term tested release, not HP/UX that was never tested in production.
>
> Some checks will be needed anyway, like function assumes that a lock is acquired in a certain function - with asserts such bugs will be narrowed-down quickly.

The Linux LTTng performance tool is basically compatible with NetBSD
dtrace hooks, ie you can use them on rump kernel code in Linux
userspace.

See https://github.com/rumpkernel/wiki/wiki/Howto%3A-Profiling-the-TCP-IP-stack-with-LTTng

And this way you end up with dtrace support under NetBSD too.

Justin