> It looks strange, but for the operating system it isn't - those threads
> (or LWPs, as the man page reads) are waiting for an event or signal, at
> which point they will swap back in.
IIRC, there was a bug about this a while ago. Essentially, the FX and
RT scheduling classes didn't implement CL
G'Day,
On Tue, Jul 01, 2008 at 01:50:45AM -0700, Sebastian Fontaine wrote:
> Hi,
>
> on my 1280 with sol10 u4 last patched on february I had 60 swapping Prozesses
> found with vmstat.
> By restarting some prozesses like apache, rpcbind etc I could eliminate 50%.
> Now I have still some left:
>
> Has anybody an Idea how I could identify the PID of the swapping prozesses?
I'm not sure why there isn't a good way of doing this. Perhaps I've
missed a more obvious approach. I would do this with mdb.
As a priviliged user, do the following:
# mdb -k
> ::walk proc pp | ::print proc_t p_swapc
45 -0700 (PDT)
> From: Sebastian Fontaine <[EMAIL PROTECTED]>
> Subject: [perf-discuss] find swapping prozess PID
> To: perf-discuss@opensolaris.org
> Errors-to: [EMAIL PROTECTED]
> Precedence: list
> X-BeenThere: perf-discuss@opensolaris.org
> Delivered-to: perf-discuss@opens
On Tue, Jul 01, 2008 at 01:50:45AM -0700, Sebastian Fontaine wrote:
> Hi,
>
> on my 1280 with sol10 u4 last patched on february I had 60 swapping Prozesses
> found with vmstat.
> By restarting some prozesses like apache, rpcbind etc I could eliminate 50%.
> Now I have still some left:
>
> >vmst
Hi,
on my 1280 with sol10 u4 last patched on february I had 60 swapping Prozesses
found with vmstat.
By restarting some prozesses like apache, rpcbind etc I could eliminate 50%.
Now I have still some left:
>vmstat 1 5
kthr memorypagedisk faults cpu
r
