Date: Sun, 26 Mar 2017 20:24:27 +0000 (UTC) From: Robert Watson <rwatson@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r316004 - head/share/man/man9 Message-ID: <201703262024.v2QKORt5067069@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: rwatson Date: Sun Mar 26 20:24:27 2017 New Revision: 316004 URL: https://svnweb.freebsd.org/changeset/base/316004 Log: Slightly improve consistency of "fooint" vs "foo_int" in DPCPU(9) examples. MFC after: 3 days Modified: head/share/man/man9/dpcpu.9 Modified: head/share/man/man9/dpcpu.9 ============================================================================== --- head/share/man/man9/dpcpu.9 Sun Mar 26 20:15:08 2017 (r316003) +++ head/share/man/man9/dpcpu.9 Sun Mar 26 20:24:27 2017 (r316004) @@ -57,20 +57,20 @@ Arbitrary C types may be used, including If no initialization is provided, then each per-CPU instance of the variable will be zero-filled (i.e., as though allocated in BSS): .Bd -literal -offset 1234 -DPCPU_DEFINE(int, fooint); +DPCPU_DEFINE(int, foo_int); .Ed .Pp Values may also be initialized statically with the definition, causing each per-CPU instance to be initialized with the value: .Bd -literal -offset 1234 -DPCPU_DEFINE(int, fooint) = 1; +DPCPU_DEFINE(int, foo_int) = 1; .Ed .Pp Syntactically, the definition may be treated as a variable. For example, a dynamic per-CPU variable may be declared as .Dv static : .Bd -literal -offset 1234 -static DPCPU_DEFINE(int, fooint); +static DPCPU_DEFINE(int, foo_int); .Ed .Pp .Fn DPCPU_DECLARE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201703262024.v2QKORt5067069>