From owner-freebsd-current  Tue Nov 13 19:34:56 2001
Delivered-To: freebsd-current@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id D97B037B416; Tue, 13 Nov 2001 19:34:53 -0800 (PST)
Received: by flood.ping.uio.no (Postfix, from userid 2602)
	id 79FD114C2E; Wed, 14 Nov 2001 04:34:52 +0100 (CET)
X-URL: http://www.ofug.org/~des/
X-Disclaimer: The views expressed in this message do not necessarily
  coincide with those of any organisation or company with
  which I am or have been affiliated.
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?
References: <XFMail.011112162431.jhb@FreeBSD.org>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 14 Nov 2001 04:34:51 +0100
In-Reply-To: <XFMail.011112162431.jhb@FreeBSD.org>
Message-ID: <xzp7ksut484.fsf@flood.ping.uio.no>
Lines: 22
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

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