search for: putnext

I am trying to use dtrace to trace all sscanf calls. I am able to use pid provider for this. But my application forks off children at times to handle requests. Is there a way I can stop the child process immediately after it is started so that I can attach a pid provider to that and trace the scanf calls in it? I have tried using the "create" probe but that did not help.

> From the department of ignorance and stupid suggestions: Run this > conversion after other passes that deal with call instructions? Yes, but my modifications are not made in a MachineFunctionPass, it's a custom inserter for an intrinsic... I'm not sure when intrinsic lowering is applied, but I guess before any MachineFunctionPass? So I'm not sure I can chosse the order at this

The following is mainly a capture of parts of multiple off-line discussions within members of the Crossbow team (Gopi, Thiru, Roamer, May-Lin, Thirumailai, Nitin, KB, ...), I thought I''d open it up to other participants. Crossbow''s core scheduling involves switching a NIC (or individual Rx rings on the NIC) to polling mode. The receive interrupt will become not only rarer,

...5 genunix ioctl 19162882 unix kstat_hold_bykid 21893794 unix putnext 23075984 e1000g e1000g_intr_pciexpress 25999320 unix i_ddi_trigger_softint 2734...

Hiya, I''m trying to track down some throughput latency that our customer seems to be attributing to our product, I can''t see what he''s talking about, but I want to try and get some deeper granularity than I might get with something like smokeping, and maybe even see if its down to something tunable on our end. I''ve been looking for some examples on how

...c_tx+302 () ffffff003e032170 dld:str_mdata_fastpath_put+a4 () ffffff003e032270 ip:udp_xmit+806 () ffffff003e032310 ip:udp_send_data+3b3 () ffffff003e032470 ip:udp_output_v4+9f9 () ffffff003e0324f0 ip:udp_send_not_connected+eb () ffffff003e032550 ip:udp_wput+fe () ffffff003e0325c0 unix:putnext+21e () ffffff003e032600 rpcmod:rpcmodwput+9b () ffffff003e032620 rpcmod:rmm_wput+1e () ffffff003e032690 unix:put+1aa () ffffff003e0326f0 rpcmod:svc_clts_ksend+1da () ffffff003e032770 rpcmod:svc_sendreply+56 () ffffff003e032a70 nfssrv:common_dispatch+6b2 () ffffff003e032a90 nfssrv:rfs_...

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org