Date: Wed, 29 Dec 2004 15:22:56 -0800 From: Nate Lawson <nate@root.org> To: Jeff Roberson <jroberson@chesapeake.net> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys ktr.h Message-ID: <41D33C50.6090109@root.org> In-Reply-To: <20041229151758.S60504@mail.chesapeake.net> References: <200412260013.iBQ0DcJ1074546@repoman.freebsd.org> <20041229020531.GA12575@dragon.nuxi.com> <41D26CE3.4070404@root.org> <20041229124826.Q60504@mail.chesapeake.net> <41D30245.8020600@root.org> <20041229151758.S60504@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff Roberson wrote: > On Wed, 29 Dec 2004, Nate Lawson wrote: >>Jeff Roberson wrote: >> >>>On Wed, 29 Dec 2004, Nate Lawson wrote: >>> >>>>Also, could someone please get us more KTR ids while they're at it? We >>>>only have 2 left. >>> >>> >>>I think we should make one or to KTR_LOCAL's or something like that. So >>>you can have a define in your file for KTR_MYCODE 0, and when you want to >>>debug it, define it to KTR_LOCAL. There are a bunch of KTR ids that are >>>used for things that don't really need to be global that we could gc if we >>>do that. >> >>Isn't there a way to dynamically allocate ids, like sysctl does for oid? > > They need to be static at compile time or they always produce massive > bloat in the kernel. Right, I thought we did something like that for other subsystems. I'm very fuzzy on the current best approach but in the past we used linker sets to gather a class of data at link time (including mod load). If the linker set was an id placeholder for a particular type of debug data, the kernel could overwrite this with the actual runtime id. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41D33C50.6090109>