hardenedbsd/HardenedBSD
1
0
Fork 0
mirror of https://git.hardenedbsd.org/hardenedbsd/HardenedBSD.git synced 2024-12-19 14:31:48 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Slightly improve consistency of "fooint" vs "foo_int" in DPCPU(9) examples.

Browse Source 
MFC after:	3 days
This commit is contained in:
Robert Watson 2017-03-26 20:24:27 +00:00
parent 8509f6321a
commit 2cb4684480
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=316004
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
share/man/man9/dpcpu.9
View File

@ -57,20 +57,20 @@ Arbitrary C types may be used, including structures and arrays.
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