From owner-freebsd-arch  Mon Apr 23 16:44:35 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from CPE-61-9-164-106.vic.bigpond.net.au (CPE-61-9-138-241.vic.bigpond.net.au [61.9.138.241])
	by hub.freebsd.org (Postfix) with ESMTP id 20C3437B422
	for <arch@freebsd.org>; Mon, 23 Apr 2001 16:44:32 -0700 (PDT)
	(envelope-from darrenr@reed.wattle.id.au)
Received: (from root@localhost)
	by CPE-61-9-164-106.vic.bigpond.net.au (8.11.0/8.11.0) id f3NNiU624919
	for <arch@freebsd.org>; Tue, 24 Apr 2001 09:44:30 +1000 (EST)
From: Darren Reed <darrenr@reed.wattle.id.au>
Message-Id: <200104232344.JAA10103@avalon.reed.wattle.id.au>
Subject: User-defined bit in sysctl flags ?
To: arch@freebsd.org
Date: Tue, 24 Apr 2001 09:44:05 +1000 (EST)
X-Mailer: ELM [version 2.4ME+ PL37 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


What do people think about having a range of bits in oid_kind that are
not used by FreeBSD but are only to be used by ``private'' sysctl handlers?

e.g.

#define CTLFLAG_PRIVATE 0x000ffff0

The idea is so you can do this:

#define SYSCTL_IPF(parent, nbr, name, access, ptr, val, descr) \
        SYSCTL_OID(parent, nbr, name, CTLTYPE_INT|access, \
                   ptr, val, sysctl_ipf_int, "I", descr);
SYSCTL_IPF(_net_inet_ipf, OID_AUTO, fr_tcpidletimeout, CTLFLAG_RW|CTL_PRIV,
           &fr_tcpidletimeout, 0, "");

and have CTL_PRIV be a bit which sysctl_ipf_int understands and not
have to worry about the value of CTL_PRIV ever being afflicted with
double-use by a FreeBSD flag because CTL_PRIV is part of CTLFLAG_PRIVATE.

Any objections to committing it to -current in the next week or so ?

Darren

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