Date: Sat, 28 Jul 2012 14:44:32 -0400 From: Ryan Stone <rysto32@gmail.com> To: Jason Hellenthal <jhellenthal@dataix.net> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Adarsh Joshi <adarsh.joshi@qlogic.com> Subject: Re: check pending callouts Message-ID: <CAFMmRNyJYDU6TT_e=uWCnJBi4Ahw3zgxEc94BzW7%2B8zR-kpAhg@mail.gmail.com> In-Reply-To: <20120728061511.GA3452@DataIX.net> References: <5E4F49720D0BAD499EE1F01232234BA87743A5E910@AVEXMB1.qlogic.org> <20120728061511.GA3452@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 28, 2012 at 2:15 AM, Jason Hellenthal <jhellenthal@dataix.net> wrote: > You should be able to dtrace that out and uncover whats going on with a > little intellect. > > The D language itself might take a little learning but it would be worth > your while to pick it up now instead of later. Actually, D isn't a great language for this type of thing because it lacks the able to loop. At dtrace.conf in April they discussed adding restricted iteration of some kind, but it sounds like it's a long way out right now. It is possible to attach kgdb to /dev/mem to do live analysis of a running kernel. Of course with callouts this may not work out so well because the callout wheel will be constantly changing out from under kgdb.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNyJYDU6TT_e=uWCnJBi4Ahw3zgxEc94BzW7%2B8zR-kpAhg>