| /f-stack/app/nginx-1.16.1/src/event/ |
| H A D | ngx_event.c | 530 if (ecf->connections > (ngx_uint_t) rlmt.rlim_cur in ngx_event_module_init() 540 ecf->connections, limit); in ngx_event_module_init() 779 cycle->connections = in ngx_event_process_init() 781 if (cycle->connections == NULL) { in ngx_event_process_init() 785 c = cycle->connections; in ngx_event_process_init() 1090 if (ecf->connections != NGX_CONF_UNSET_UINT) { in ngx_event_connections() 1095 ecf->connections = ngx_atoi(value[1].data, value[1].len); in ngx_event_connections() 1096 if (ecf->connections == (ngx_uint_t) NGX_ERROR) { in ngx_event_connections() 1103 cf->cycle->connection_n = ecf->connections; in ngx_event_connections() 1286 ecf->connections = NGX_CONF_UNSET_UINT; in ngx_event_core_create_conf() [all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A D | coresight-cti.yaml | 18 The CTI component properties define the connections between the individual 28 described in the bindings as the actual connections are software 31 In general the connections between CTI and components via the trigger signals 35 In this case the ARM v8 architecture defines the required signal connections 45 on the connections between the CTI and other components for correct operation. 48 configuration). These registers may be used to explore the trigger connections 132 A trigger connections child node which describes the trigger signals 233 # v8 architecturally defined CTI - CPU + ETM connections generated by the 247 # Implementation defined CTI - CPU + ETM connections explicitly defined.. 294 # Implementation defined CTI - non CoreSight component connections.
|
| /f-stack/freebsd/netinet/libalias/ |
| H A D | HISTORY | 6 - Host accepts incoming connections for ports 0 to 1023. 13 connections (no more 0 to 1023 restriction). 41 - Accepts FTP data connections from other than 42 port 20. This allows one ftp connections 127 bypass of FTP/IRC DCC data connections. Also added
|
| /f-stack/freebsd/contrib/device-tree/Bindings/ |
| H A D | graph.txt | 7 control flow to devices, but there can be more complex connections between 11 phandle properties pointing to other nodes to describe connections that 18 type of the connections, they just map their existence. Specific properties 24 the connecting data buses. A single port with multiple connections can
|
| /f-stack/freebsd/contrib/device-tree/Bindings/display/ |
| H A D | allwinner,sun4i-a10-display-engine.yaml | 21 For all connections between components up to the TCONs in the 36 represent the connections between the components, while the numbers 39 The same rule also applies to DE 2.0 mixer-TCON connections:
|
| /f-stack/app/redis-5.0.5/tests/unit/ |
| H A D | limits.tcl | 2 test {Check if maxclients works refusing connections} {
|
| /f-stack/freebsd/contrib/device-tree/Bindings/sound/ |
| H A D | qcom,apq8096.txt | 13 Definition: A list of the connections between audio components. 90 qcom,audio-routing: A list of the connections between audio components.
|
| H A D | mt2701-wm8960.txt | 6 - audio-routing: a list of the connections between audio
|
| H A D | atmel-at91sam9g20ek-wm8731-audio.txt | 6 - atmel,audio-routing: A list of the connections between audio components.
|
| H A D | atmel-sam9x5-wm8731-audio.txt | 8 - atmel,audio-routing: A list of the connections between audio components.
|
| H A D | mxs-audio-sgtl5000.txt | 8 - audio-routing : A list of the connections between audio components.
|
| H A D | mt2701-cs42448.txt | 6 - audio-routing: a list of the connections between audio
|
| H A D | atmel-wm8904.txt | 6 - atmel,audio-routing: A list of the connections between audio components.
|
| H A D | nvidia,tegra-audio-wm9712.txt | 12 - nvidia,audio-routing : A list of the connections between audio components.
|
| H A D | omap-twl4030.txt | 12 - ti,audio-routing: List of connections between audio components.
|
| H A D | nvidia,tegra-audio-wm8753.txt | 12 - nvidia,audio-routing : A list of the connections between audio components.
|
| H A D | rockchip,rk3288-hdmi-analog.txt | 9 - rockchip,routing: A list of the connections between audio components.
|
| H A D | imx-audio-sgtl5000.txt | 13 - audio-routing : A list of the connections between audio components.
|
| H A D | nvidia,tegra-audio-alc5632.txt | 12 - nvidia,audio-routing : A list of the connections between audio components.
|
| H A D | samsung,tm2-audio.txt | 15 - samsung,audio-routing : a list of the connections between audio components;
|
| H A D | nvidia,tegra-audio-sgtl5000.txt | 12 - nvidia,audio-routing : A list of the connections between audio components.
|
| /f-stack/freebsd/netgraph/bluetooth/include/ |
| H A D | ng_btsocket.h | 156 ng_hci_node_con_ep *connections; member 302 ng_l2cap_node_con_ep *connections; member
|
| /f-stack/freebsd/contrib/device-tree/Bindings/display/connector/ |
| H A D | vga-connector.txt | 15 The VGA connector internal connections are modeled using the OF graph bindings
|
| /f-stack/freebsd/contrib/vchiq/interface/vchi/ |
| H A D | vchi.h | 152 …SERVICE_INIT)(VCHI_INSTANCE_T initialise_instance, VCHI_CONNECTION_T **connections, uint32_t num_c… 177 extern int32_t vchi_connect( VCHI_CONNECTION_T **connections,
|
| /f-stack/freebsd/contrib/device-tree/Bindings/display/bridge/ |
| H A D | simple-bridge.yaml | 35 This device has two video ports. Their connections are modeled using the
|