From owner-freebsd-smp  Mon Oct  9  7: 5: 1 2000
Delivered-To: freebsd-smp@freebsd.org
Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4EC1F37B502; Mon,  9 Oct 2000 07:04:54 -0700 (PDT)
Received: from berserker.bsdi.com (cp@localhost [127.0.0.1])
	by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id HAA06839;
	Mon, 9 Oct 2000 07:40:56 -0600 (MDT)
Message-Id: <200010091340.HAA06839@berserker.bsdi.com>
To: John Baldwin <jhb@freebsd.org>
Cc: Bob Bishop <rb@gid.co.uk>, smp@freebsd.org
Subject: Re: Options with SMPng 
In-reply-to: Your message of "Sun, 08 Oct 2000 23:07:52 PDT."
             <200010090607.XAA03206@john.baldwin.cx> 
From: Chuck Paterson <cp@bsdi.com>
Date: Mon, 09 Oct 2000 07:40:56 -0600
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

	I think we ought to dump the KTR_EXTEND stuff. This makes
the kernel run soo slow that it isn't really usable. Without
KTR_EXTEND the penalty is minor.

John Baldwin wrote on: Sun, 08 Oct 2000 23:07:52 PDT
}
}(if you want the KTR tracing stuff:)
}options         KTR
}options         KTR_EXTEND
}options         KTR_COMPILE=0x3fffff
}options         KTR_MASK=(KTR_INTR|KTR_PROC)
}options         KTR_ENTRIES=1024  # or some other power of 2
}
}KTR is only useful during panics when you can dump the trace
}buffer, or if you are doiing remote kgdb, or ddb on a running
}kernel.
}
}-- 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message