Date: 14 Nov 2001 04:34:51 +0100 From: Dag-Erling Smorgrav <des@ofug.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Julian Elischer <julian@elischer.org>, freebsd-current@FreeBSD.ORG, Steve Kargl <sgk@troutmask.apl.washington.edu>, Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Subject: Re: namespace pollution with struct thread? Message-ID: <xzp7ksut484.fsf@flood.ping.uio.no> In-Reply-To: <XFMail.011112162431.jhb@FreeBSD.org> References: <XFMail.011112162431.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin <jhb@FreeBSD.org> writes: > On 12-Nov-01 Julian Elischer wrote: > > On the other hand we might conceivably be able to > > stop the export from the kernel of this struct type. > Not unless we stop exporting struct proc since each proc has an > embedded thread. We don't really need to export struct proc now that we have struct kinfo_proc, do we? The few userland libraries and programs that still need it (basically libkvm and gdb - libkvm consumers such as top only need to have it declared, not defined) could define something like _NEED_STRUCT_PROC before including <sys/proc.h>. One other thing worth pointing out is that there is no reason for <sys/user.h> to include <sys/proc.h>. It just needs to declare struct proc as an opaque structure. Also, <sys/user.h> currently pulls in a lot of other headers such as <sys/_lock.h> and <sys/_mutex.h> that are needed only because <sys/proc.h> depends on them. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp7ksut484.fsf>