search for: lwpid

when check java process lock statistics, plockstat failed, please see below: # prstat -mLp 21162 PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWPID 21162 7677 0.9 0.1 0.0 0.0 0.0 99 0.0 0.3 83 89 215 0 java/81 21162 7677 0.3 0.1 0.0 0.0 0.0 0.0 99 0.2 106 33 305 0 java/35 21162 7677 0.1 0.0 0.0 0.0 0.0 100 0.0 0.1 79 6 85 0 java/59 21162 7677 0.1 0.0 0.0 0.0 0.0 100 0.0 0.0 51 2 63 0 java/61 21162 7677...

[Just starting out with DTrace and was hoping to get some guidance.] I have a "benchmark" program that I monitored with both prstat (prstat -mL -P <PID>) and pfilestat (from the DTrace toolkit). Prstat reports LAT values in the 0.1-0.2% range, but pfilestat reports "waitcpu" values in the 6-10%. Since those two numbers supposedly represent time waiting for the CPU,

...? (in /usr/lib/valgrind/memcheck-amd64-linux) > ==20179== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) > ==20179== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) > > sched status: > running_tid=1 > > Thread 1: status = VgTs_Runnable (lwpid 20179) > ==20179== at 0x5DE7E00: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) > ==20179== by 0x5DC70BF: EC_POINT_mul (in > /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) > ==20179== by 0x5DC5F06: EC_POINT_new (in > /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) > ==20179==...

...nux) ==20179== by 0x380D296B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==20179== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==20179== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 20179) ==20179== at 0x5DE7E00: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==20179== by 0x5DC70BF: EC_POINT_mul (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==20179== by 0x5DC5F06: EC_POINT_new (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==20179== by 0x5823876: dcrypt_openssl...

...check-amd64-linux) >> ==20179== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) >> ==20179== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) >> >> sched status: >> running_tid=1 >> >> Thread 1: status = VgTs_Runnable (lwpid 20179) >> ==20179== at 0x5DE7E00: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) >> ==20179== by 0x5DC70BF: EC_POINT_mul (in >> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) >> ==20179== by 0x5DC5F06: EC_POINT_new (in >> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0...

http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. * master: Removed hardcoded 511 backlog limit for listen(). The kernel should limit this as needed. * doveadm import: Source user is now initialized

http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. * master: Removed hardcoded 511 backlog limit for listen(). The kernel should limit this as needed. * doveadm import: Source user is now initialized