• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 Glukacs1 commented Permalink

Hi Chris. <div>&nbsp;</div> I know only one online way to check this in case you specified the CPU for a PID (like you did with the bindprocessor): <div>&nbsp;</div> Under kdb you can you use the 'tpid -d [PID]' command like that way: <div>&nbsp;</div> # ps -ef |grep db2 <br /> root 5701816 1 0 17 Jun - 0:24 /usr/opt/db2_08_01/bin/db2fmcd <br /> # bindprocessor 5701816 3 <br /> ps -o THREAD -p 5701816 <br /> USER PID PPID TID ST CP PRI SC WCHAN F TT BND COMMAND <br /> root 5701816 1 - A 0 60 1 f1000110095cacb0 240401 - <b>3</b> /usr/opt/db2_08_01/bin/db2fmcd <div>&nbsp;</div> # kdb <br /> .... <br /> (0)&gt; tpid -d 5701816 <br /> SLOT NAME STATE TID PRI RQ CPUID CL WCHAN <div>&nbsp;</div> pvthread+00D800 216 db2fmcd SLEEP D800B3 03C 3 <b>00003</b> 0 F1000110081F78B0

2 cggibbo commented Permalink

Thanks Glukacs1. Yes, if you bind a process to a logical processor, it's easy to find out which processor number your process is running on. But if you are not using bindprocessor....then I don't know. So far, trace is the only tool that seems to provide this information. I'll keep looking and if I find out I will update this post. <div>&nbsp;</div> Thanks again for your feedback.

Add a Comment Add a Comment