| /freebsd/sbin/ipf/libipf/ |
| H A D | printnatside.c | 11 printnatside(char *side, nat_stat_side_t *ns) in printnatside() argument
13 PRINTF("%lu\tproxy create fail %s\n", ns->ns_appr_fail, side); in printnatside()
14 PRINTF("%lu\tproxy fail %s\n", ns->ns_ipf_proxy_fail, side); in printnatside()
15 PRINTF("%lu\tbad nat %s\n", ns->ns_badnat, side); in printnatside()
16 PRINTF("%lu\tbad nat new %s\n", ns->ns_badnatnew, side); in printnatside()
17 PRINTF("%lu\tbad next addr %s\n", ns->ns_badnextaddr, side); in printnatside()
18 PRINTF("%lu\tbucket max %s\n", ns->ns_bucket_max, side); in printnatside()
19 PRINTF("%lu\tclone nomem %s\n", ns->ns_clone_nomem, side); in printnatside()
20 PRINTF("%lu\tdecap bad %s\n", ns->ns_decap_bad, side); in printnatside()
21 PRINTF("%lu\tdecap fail %s\n", ns->ns_decap_fail, side); in printnatside()
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/interrupt-controller/ |
| H A D | fsl,mu-msi.yaml | 16 for one processor (A side) to signal the other processor (B side) using
20 different clocks (from each side of the different peripheral buses).
21 Therefore, the MU must synchronize the accesses from one side to the
23 registers (Processor A-side, Processor B-side).
40 - description: a side register base address
41 - description: b side register base address
45 - const: processor-a-side
46 - const: processor-b-side
49 description: a side interrupt number.
57 - description: a side power domain
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/IR/ |
| H A D | FixedPointBuilder.h | 224 /// \p LHS - The left hand side
225 /// \p LHSSema - The semantic of the left hand side
226 /// \p RHS - The right hand side
227 /// \p RHSSema - The semantic of the right hand side
250 /// \p LHS - The left hand side
251 /// \p LHSSema - The semantic of the left hand side
252 /// \p RHS - The right hand side
253 /// \p RHSSema - The semantic of the right hand side
284 /// \p LHS - The left hand side
285 /// \p LHSSema - The semantic of the left hand side
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/devfreq/ |
| H A D | rk3399_dmc.txt | 77 the ODT on the DRAM side and controller side are
81 the DRAM side driver strength in ohms. Default
85 the DRAM side ODT strength in ohms. Default value
89 the phy side CA line (incluing command line,
94 the PHY side DQ line (including DQS/DQ/DM line)
98 the PHY side ODT strength. Default value is 240.
103 the ODT on the DRAM side and controller side are
107 the DRAM side driver strength in ohms. Default
111 the DRAM side ODT strength in ohms. Default value
115 the PHY side CA line (including command line,
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/powerpc/power8/ |
| H A D | translation.json | 29 …r chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a data side request",
35 …r chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a data side request",
41 …ion": "A Page Table Entry was loaded into the TLB from local core's L2 due to a data side request",
47 …as loaded into the TLB from a localtion other than the local core's L2 due to a data side request",
53 …TLB from local core's L2 hit without dispatch conflicts on Mepf state. due to a data side request",
59 …le Entry was loaded into the TLB from local core's L2 without conflict due to a data side request",
65 …ion": "A Page Table Entry was loaded into the TLB from local core's L3 due to a data side request",
71 …ry was loaded into the TLB from local core's L3 with dispatch conflict due to a data side request",
77 …TLB from local core's L3 without dispatch conflicts hit on Mepf state. due to a data side request",
83 …le Entry was loaded into the TLB from local core's L3 without conflict due to a data side request",
[all …]
|
| H A D | frontend.json | 293 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a instruction side request",
299 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a instruction side request",
305 …B from another chip's L4 on a different Node or Group (Distant) due to a instruction side request",
311 … from another chip's memory on the same Node or Group (Distant) due to a instruction side request",
317 …A Page Table Entry was loaded into the TLB from local core's L2 due to a instruction side request",
323 …ed into the TLB from a localtion other than the local core's L2 due to a instruction side request",
329 …m local core's L2 hit without dispatch conflicts on Mepf state. due to a instruction side request",
335 …y was loaded into the TLB from local core's L2 without conflict due to a instruction side request",
341 …A Page Table Entry was loaded into the TLB from local core's L3 due to a instruction side request",
347 …ed into the TLB from a localtion other than the local core's L3 due to a instruction side request",
[all …]
|
| H A D | marked.json | 365 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data side request",
371 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data side request",
377 …B from another chip's L4 on a different Node or Group (Distant) due to a marked data side request",
383 … from another chip's memory on the same Node or Group (Distant) due to a marked data side request",
389 …A Page Table Entry was loaded into the TLB from local core's L2 due to a marked data side request",
395 …ed into the TLB from a localtion other than the local core's L2 due to a marked data side request",
401 …m local core's L2 hit without dispatch conflicts on Mepf state. due to a marked data side request",
407 …y was loaded into the TLB from local core's L2 without conflict due to a marked data side request",
413 …A Page Table Entry was loaded into the TLB from local core's L3 due to a marked data side request",
419 …ed into the TLB from a localtion other than the local core's L3 due to a marked data side request",
[all …]
|
| /freebsd/tools/regression/poll/l/ |
| H A D | sockpoll.out | 5 ok 4 state other side after large write: expected POLLIN | POLLOUT; got POLLIN | POLLOUT
6 not ok 5 state other side after close: expected POLLIN | POLLHUP; got POLLIN | POLLOUT | POLLHUP
7 not ok 6 state other side after reading input: expected POLLHUP; got POLLIN | POLLOUT | POLLHUP
9 ok 8 state other side after shutdown(SHUT_WR): expected POLLIN | POLLOUT; got POLLIN | POLLOUT
10 ok 9 state other side after reading EOF: expected POLLIN | POLLOUT; got POLLIN | POLLOUT
11 ok 10 state after data from other side: expected POLLIN | POLLOUT; got POLLIN | POLLOUT
17 ok 16 state other side after shutdown(SHUT_RD): expected POLLOUT; got POLLOUT
19 not ok 18 state other side after shutdown(SHUT_WR): expected POLLIN | POLLOUT; got POLLIN | POLLOUT…
20 ok 19 state other side after shutdown(SHUT_RD): expected POLLOUT; got POLLOUT
21 ok 20 state other side after write: expected POLLIN | POLLOUT; got POLLIN | POLLOUT
[all …]
|
| /freebsd/tools/regression/poll/14/ |
| H A D | sockpoll.out | 5 ok 4 state other side after large write: expected POLLIN | POLLOUT; got POLLIN | POLLOUT
6 ok 5 state other side after close: expected POLLIN | POLLHUP; got POLLIN | POLLHUP
7 not ok 6 state other side after reading input: expected POLLHUP; got POLLIN | POLLHUP
9 ok 8 state other side after shutdown(SHUT_WR): expected POLLIN | POLLOUT; got POLLIN | POLLOUT
10 ok 9 state other side after reading EOF: expected POLLIN | POLLOUT; got POLLIN | POLLOUT
11 ok 10 state after data from other side: expected POLLIN | POLLOUT; got POLLIN | POLLOUT
17 ok 16 state other side after shutdown(SHUT_RD): expected POLLOUT; got POLLOUT
19 ok 18 state other side after shutdown(SHUT_WR): expected POLLIN | POLLOUT; got POLLIN | POLLOUT
20 ok 19 state other side after shutdown(SHUT_RD): expected POLLOUT; got POLLOUT
21 ok 20 state other side after write: expected POLLIN | POLLOUT; got POLLIN | POLLOUT
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/memory-controllers/ |
| H A D | rockchip,rk3399-dmc.yaml | 132 the ODT on the DRAM side and controller side are both disabled.
138 When the DRAM type is DDR3, this parameter defines the DRAM side drive
146 When the DRAM type is DDR3, this parameter defines the DRAM side ODT
154 When the DRAM type is DDR3, this parameter defines the phy side CA line
162 When the DRAM type is DDR3, this parameter defines the PHY side DQ line
170 When the DRAM type is DDR3, this parameter defines the PHY side ODT
180 ODT on the DRAM side and controller side are both disabled.
186 When the DRAM type is LPDDR3, this parameter defines the DRAM side driv
[all...] |
| /freebsd/lib/libpmc/pmu-events/arch/x86/silvermont/ |
| H A D | virtual-memory.json | 13 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)",
22 "BriefDescription": "Duration of D-side page-walks in core cycles",
26 …"PublicDescription": "This event counts every cycle when a D-side (walks due to a load) page walk …
31 "BriefDescription": "D-side page-walks",
41 "BriefDescription": "Duration of I-side page-walks in core cycles",
45 …"PublicDescription": "This event counts every cycle when a I-side (walks due to an instruction fet…
50 "BriefDescription": "I-side page-walks",
60 "BriefDescription": "Total page walks that are completed (I-side and D-side)",
|
| /freebsd/share/examples/ppp/ |
| H A D | login-auth | 49 pack .l.prompt -side left;
53 pack .l.value -side right;
55 pack .l -side top -padx $fxpad -pady $fypad;
60 pack .p.prompt -side left;
63 pack .p.value -side right;
66 pack .p -side top -padx $fxpad -pady $fypad;
70 pack .b.ok -side left;
72 pack .b.cancel -side right;
73 pack .b -side top -padx $fxpad -pady $fypad;
|
| H A D | chap-auth | 52 pack .$n.prompt -side left;
62 pack .$n.value -side right;
70 pack .$n -side top -padx $fxpad -pady $fypad;
86 pack .k.value -side right;
89 pack .k -side top -padx $fxpad -pady $fypad;
93 pack .b.ok -side left;
95 pack .b.cancel -side right;
96 pack .b -side top -padx $fxpad -pady $fypad;
|
| /freebsd/usr.bin/rpcgen/ |
| H A D | rpcgen.1 | 77 server-side stubs in
79 and client-side stubs in
106 then the client side sample file is written to
108 the server side sample file to
213 defined when compiling into server-side stubs
215 defined when compiling into client-side stubs
299 in the server side stubs.
355 Compile into client-side stubs.
362 Compile into server-side stubs,
377 functions are not yet MT-safe, which means that rpcgen generated server-side
[all …]
|
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | cond-token-var.mk | 20 # A defined variable may appear on either side of the comparison.
28 # A variable that appears on the left-hand side must be defined.
34 # A variable that appears on the right-hand side must be defined.
58 # A defined variable may appear on either side of the comparison.
62 # A variable on the left-hand side must be defined.
67 # A variable on the right-hand side must be defined.
104 # The left-hand side of a comparison must not be an unquoted word.
109 # The left-hand side of a comparison must not be an unquoted word.
114 # The left-hand side of a comparison must not be an unquoted word.
|
| H A D | parse-var.mk | 53 # in a condition, left-hand side, unquoted
54 # in a condition, left-hand side, quoted
55 # in a condition, right-hand side, unquoted
56 # in a condition, right-hand side, quoted
57 # left-hand side of a variable assignment
58 # right-hand side of a ':=' variable assignment
59 # right-hand side of a '!=' variable assignment
75 # What other side effects are there?
80 # side of the assignment, but only if they occur inside expressions.
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/knightslanding/ |
| H A D | virtual-memory.json | 22 …"BriefDescription": "Counts the total number of core cycles for all the D-side page walks. The cyc…
30 …"BriefDescription": "Counts the total D-side page walks that are completed or started. The page wa…
39 …"BriefDescription": "Counts the total number of core cycles for all the I-side page walks. The cyc…
43 …"PublicDescription": "This event counts every cycle when an I-side (walks due to an instruction fe…
48 "BriefDescription": "Counts the total I-side page walks that are completed.",
57 "BriefDescription": "Counts the total page walks that are completed (I-side and D-side)",
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | provider-digest.pod | 100 OSSL_FUNC_digest_newctx() should create and return a pointer to a provider side
107 OSSL_FUNC_digest_freectx() is passed a pointer to the provider side digest context in
111 OSSL_FUNC_digest_dupctx() should duplicate the provider side digest context in the
117 provider side digest context in the I<dctx> parameter.
124 side context.
131 The I<dctx> parameter contains a pointer to the provider side context.
137 No provider side digest context is used.
153 provider side digest context I<dctx> to I<params>.
158 the given provider side digest context I<dctx> and stores them in I<params>.
170 the provider side context if I<dctx> is not NULL and on the provider
[all …]
|
| H A D | provider-mac.pod | 93 OSSL_FUNC_mac_newctx() should create and return a pointer to a provider side
100 OSSL_FUNC_mac_freectx() is passed a pointer to the provider side mac context in
106 OSSL_FUNC_mac_dupctx() should duplicate the provider side mac context in the
112 side mac context in the I<mctx> parameter. The I<params> are set before setting
118 side context.
123 The I<mctx> parameter contains a pointer to the provider side context.
138 provider side mac context I<mctx> to I<params>.
143 associated with the given provider side mac context I<mctx> and stores them
153 with the provider side context I<mctx> in its current state if it is
155 provider side algorithm I<provctx>.
[all …]
|
| /freebsd/contrib/ofed/librdmacm/man/ |
| H A D | rdma_accept.3 | 18 Called from the listening side to accept a connection or datagram
44 copied and transparently passed to the remote side as part of the
48 amount of data transferred to the remote side is transport dependent and may
52 local side will accept from the remote side. Applies only to RDMA_PS_TCP.
58 local side will have to the remote side. Applies only to RDMA_PS_TCP.
87 by the active side of the connection. The HCA ACK delay is a property of
|
| H A D | rdma_connect.3 | 33 copied and transparently passed to the remote side as part of the
37 amount of data transferred to the remote side is transport dependent and may
41 local side will accept from the remote side. Applies only to RDMA_PS_TCP.
47 local side will have to the remote side. Applies only to RDMA_PS_TCP.
88 active side of the connection send the first message.
|
| /freebsd/lib/libpmc/pmu-events/arch/powerpc/power9/ |
| H A D | translation.json | 25 …m another chip's memory on the same Node or Group (Distant) due to a data side request. When using…
35 …chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a instruction side request"
60 … or L3 on a different Node or Group (Distant), as this chip due to a data side request. When using…
75 …ared or modified data from another core's L2/L3 on the same chip due to a instruction side request"
100 …e TLB from another chip's L4 on the same Node or Group ( Remote) due to a instruction side request"
145 …from a memory location including L4 from local remote or distant due to a instruction side request"
150 …rom another core's L2/L3 on a different chip (remote or distant) due to a instruction side request"
165 … or L3 on a different Node or Group (Distant), as this chip due to a data side request. When using…
185 …om another chip's L4 on a different Node or Group (Distant) due to a data side request. When using…
210 …chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a instruction side request"
[all …]
|
| H A D | pipeline.json | 35 …her chip's L4 on a different Node or Group (Distant) due to a marked data side request. When using…
40 …s loaded into the TLB from local core's L2 without conflict due to a data side request. When using…
80 …ied (M) data from another core's L2 on the same chip due to a marked data side request. When using…
95 …h Modified (M) data from another core's L2 on the same chip due to a data side request. When using…
115 …e's L3 without dispatch conflicts hit on Mepf state. due to a marked data side request. When using…
160 …core's L2/L3 on a different chip (remote or distant) due to a marked data side request. When using…
175 …ed into the TLB from local core's L3 with dispatch conflict due to a data side request. When using…
180 …d into the TLB from local core's L2 without conflict due to a marked data side request. When using…
225 …d into the TLB from local core's L3 without conflict due to a marked data side request. When using…
250 …s L2 or L3 on the same Node or Group (Remote), as this chip due to a data side request. When using…
[all …]
|
| /freebsd/share/doc/psd/15.yacc/ |
| H A D | ss4 | 107 the right hand side of a grammar rule,
109 an instance of the rule, replacing the right hand side
110 by the left hand side.
139 symbols on the right hand side (three in this case).
143 right side of the rule).
155 on the left side of the rule, perform what is in
174 state where the right hand side of the rule was first seen.
175 The parser then behaves as if it had seen the left side at that time.
176 If the right hand side of the rule is empty,
320 This rule has two symbols on the right hand side, so
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | provider-digest.7 | 236 \&\fBOSSL_FUNC_digest_newctx()\fR should create and return a pointer to a provider side
243 \&\fBOSSL_FUNC_digest_freectx()\fR is passed a pointer to the provider side digest context in
247 \&\fBOSSL_FUNC_digest_dupctx()\fR should duplicate the provider side digest context in the
252 provider side digest context in the \fIdctx\fR parameter.
259 side context.
266 The \fIdctx\fR parameter contains a pointer to the provider side context.
272 No provider side digest context is used.
287 provider side digest context \fIdctx\fR to \fIparams\fR.
292 the given provider side digest context \fIdctx\fR and stores them in \fIparams\fR.
304 the provider side context if \fIdctx\fR is not \s-1NULL\s0 and on the provider
[all …]
|