Re: [perf-discuss] tcp_listendrop

2010-05-04 Thread Gopi Desaboyina
Yes. also check with below command to find out which port is getting more connections & dropping them out. use "ndd /dev/tcp tcp_listen_hash" right-most column to see if you're hitting the queue max -- This message posted from opensolaris.org ___ perf-

Re: [perf-discuss] pid$target: Not enough space

2010-05-04 Thread Jianhua Yang
I'll try that. Thank you very much for your info ! Jianhua Yang -Original Message- From: perf-discuss-boun...@opensolaris.org [mailto:perf-discuss-boun...@opensolaris.org] On Behalf Of johan...@opensolaris.org Sent: Tuesday, May 04, 2010 8:

Re: [perf-discuss] pid$target: Not enough space

2010-05-04 Thread johansen
On Tue, May 04, 2010 at 03:23:09PM -0700, Jianhua Yang wrote: > I wanted to find out what the single threaded process was doing with dtrace > but it returned with "Not enough space"error: > > # dtrace -ln 'pid$target:::entry,pid$target:::return {trace(timestamp);}' -p > 25050 > dtrace: invalid p

[perf-discuss] pid$target: Not enough space

2010-05-04 Thread Jianhua Yang
I wanted to find out what the single threaded process was doing with dtrace but it returned with "Not enough space"error: # dtrace -ln 'pid$target:::entry,pid$target:::return {trace(timestamp);}' -p 25050 dtrace: invalid probe specifier pid$target:::entry,pid$target:::return {trace(timestamp);}