Thanks Jim.
> Threads are put to sleep when they issue blocking
> system calls.
> I'm not sure exactly what you mean by "only know
> synchronous
> app wait from an app perspective", but the
> threads will be in the
> sleep state (SLP) after issuing the read/write until
> the data is
> availabl
example that uses open64 here:
>
> http://wikis.sun.com/display/DTrace/Speculative+Traci
> ng
>
> You could adapt this to use forksys instead. This
> would allow you to
> see just where in the kernel your fork is actually
> failing.
>
> -j
>
OK. I go ahead an
I was wondering if a fork failure with EAGAIN will manifest as an allocation
failure in vmem, if so how to see that and if there is a specifc cache that can
be tweaked. At present the only cache that is reporting any failure is
kmem_lp 1002438656 1002438656 239 1858
thank
can someone explain on how LGRP_LOADAVG_IN_THREAD_MAX is used in loadaverage
calc? Thanks
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/os/clock.c#genloadavg
avg = hr_avg / (NANOSEC / LGRP_LOADAVG_IN_THREAD_MAX);
http://src.opensolaris.org/source/xref/onnv/onnv-gate
