Date: Fri, 20 Jan 2006 01:19:55 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Julian Elischer <julian@elischer.org> Cc: current@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: kernel thread as real threads.. Message-ID: <20060120061955.GA8687@xor.obsecurity.org> In-Reply-To: <43D0715A.7020302@elischer.org> References: <43D05151.5070409@elischer.org> <20060120030105.GA5286@xor.obsecurity.org> <43D0715A.7020302@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Jan 19, 2006 at 09:12:58PM -0800, Julian Elischer wrote: > >What about that threads don't show CPU usage or accumulate CPU time? > >This is annoying enough for user threads but would be a pretty serious > >usability limitation if it happened for kernel threads too. > > > >Kris > > > > > > the example I showed was the 'ps' from ddb which of course doesn't show > any stats anyhow. Yeah, I know that, but they're also not displayed in ps(1) or top(1), etc. Kris > Well, stats are collected. It is just a case of getting them out and > displayed.. > It's kind of meaningless in KSE type threads but for libthr and kernel > threads it would have meaning. > > Anynow I just want to see what it takes to not have 40 extra proc > structs hanging around. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0IEKWry0BWjoQKURAmA5AJ9C906J6t+C5DpP/qj3nr0r/p+wUACgxTOs S7dd7Z1o2qZLpuh5GOUflbY= =VVrF -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060120061955.GA8687>