Date: Tue, 24 Apr 2001 09:44:05 +1000 (EST) From: Darren Reed <darrenr@reed.wattle.id.au> To: arch@freebsd.org Subject: User-defined bit in sysctl flags ? Message-ID: <200104232344.JAA10103@avalon.reed.wattle.id.au>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104232344.JAA10103>