From owner-freebsd-net@FreeBSD.ORG  Sat Jul 28 18:44:38 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C70B31065670
	for <freebsd-net@freebsd.org>; Sat, 28 Jul 2012 18:44:38 +0000 (UTC)
	(envelope-from rysto32@gmail.com)
Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com
	[209.85.220.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 7EC7A8FC08
	for <freebsd-net@freebsd.org>; Sat, 28 Jul 2012 18:44:38 +0000 (UTC)
Received: by vcbgb22 with SMTP id gb22so4376708vcb.13
	for <freebsd-net@freebsd.org>; Sat, 28 Jul 2012 11:44:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=zkORXZ5ywTFj+S+d7plehBQcLGP0ciwUF+wwnzTKRWM=;
	b=gI4qDd6V6vreDbzovwIfRqfgmoAbGKAvJzIrfP5FzMucoMk4uvf5OI6DwHiuY4vvEg
	17Q7oIglOChYIrFPpQFo6e5JTuAkshAiEMRBtuF3O4N8Exr3CJGmq2sFD/BcNNuZA+JW
	7Rf44cSPhko9csoHuQwJe9kZ7xUrnOEcppIeIS0cgjBNCJSPQpTk4IoBOcxDRfBRugO6
	L2SOCdrE986iKSVZNO7KsEQdKtLs4Unq4VqYozg8lHtGPzefMjpoCKVDjLGZnQZ0VmI3
	qiLeeFLiH96OCWyrHZ7hVWju3/Iss1yMGFQmWn70AlCVUNDPBsy5PIIROAMXnkCvzdVE
	Bukw==
MIME-Version: 1.0
Received: by 10.220.152.138 with SMTP id g10mr6275618vcw.14.1343501072621;
	Sat, 28 Jul 2012 11:44:32 -0700 (PDT)
Received: by 10.58.12.202 with HTTP; Sat, 28 Jul 2012 11:44:32 -0700 (PDT)
In-Reply-To: <20120728061511.GA3452@DataIX.net>
References: <5E4F49720D0BAD499EE1F01232234BA87743A5E910@AVEXMB1.qlogic.org>
	<20120728061511.GA3452@DataIX.net>
Date: Sat, 28 Jul 2012 14:44:32 -0400
Message-ID: <CAFMmRNyJYDU6TT_e=uWCnJBi4Ahw3zgxEc94BzW7+8zR-kpAhg@mail.gmail.com>
From: Ryan Stone <rysto32@gmail.com>
To: Jason Hellenthal <jhellenthal@dataix.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>,
	Adarsh Joshi <adarsh.joshi@qlogic.com>
Subject: Re: check pending callouts
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jul 2012 18:44:38 -0000

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.