Home
last modified time | relevance | path

Searched refs:scheme (Results 1 – 25 of 76) sorted by relevance

1234

/f-stack/dpdk/drivers/net/dpaa/
H A Ddpaa_fmc.c232 if (!fmc->scheme[idx].override_storage_profile && in dpaa_port_fmc_scheme_parse()
240 fmc->scheme[idx].next_engine) { in dpaa_port_fmc_scheme_parse()
241 for (i = 0; i < fmc->scheme[idx] in dpaa_port_fmc_scheme_parse()
248 fmc->scheme[idx].override_storage_profile && in dpaa_port_fmc_scheme_parse()
249 fmc->scheme[idx].storage_profile.direct && in dpaa_port_fmc_scheme_parse()
250 fmc->scheme[idx].storage_profile in dpaa_port_fmc_scheme_parse()
261 !fmc->scheme[idx].override_storage_profile) { in dpaa_port_fmc_scheme_parse()
267 fmc->scheme[idx].override_storage_profile && in dpaa_port_fmc_scheme_parse()
268 fmc->scheme[idx].storage_profile.direct && in dpaa_port_fmc_scheme_parse()
269 fmc->scheme[idx].storage_profile in dpaa_port_fmc_scheme_parse()
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/mtd/
H A Dgpmc-nand.txt35 Refer below "How to select correct ECC scheme for your device ?"
105 How to select correct ECC scheme for your device ?
107 Higher ECC scheme usually means better protection against bit-flips and
108 increased system lifetime. However, selection of ECC scheme is dependent
120 Other factor which governs the selection of ecc-scheme is oob-size.
137 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
144 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
147 (OOBSIZE=128). So this device can use BCH16 ecc-scheme.
/f-stack/freebsd/contrib/zlib/doc/
H A Dtxtvsbin.txt16 were using a crude detection scheme: if more than 80% (4/5) of the bytes
19 limitation of this scheme is the restriction to Latin-based alphabets.
22 are most often misidentified by this scheme; in other words, the rate
24 is low. Another weakness of this scheme is a reduced precision, due to
28 In this article we propose a new, simple detection scheme that features
29 a much increased precision and a near-100% recall. This scheme is
88 considerations. In such cases, a scheme that tolerates a small fraction
/f-stack/dpdk/doc/guides/prog_guide/
H A Dprofile_app.rst71 scheme.
87 The PMU based scheme is useful for high accuracy performance profiling with
89 Linux userspace profiling tools like ``perf`` as this scheme alters the PMU
H A Dgraph_lib.rst40 - The modular scheme allows having reusable nodes for the consumers.
41 - The modular scheme allows us to abstract the vendor HW specific
133 using the constructor scheme. The constructor scheme used here to support multi-process.
152 This is a use case to address the static node scheme where one knows upfront the
H A Defd_lib.rst53 In this scheme (:numref:`figure_efd1`), the front end server/distributor/load balancer
55 this flow should be directed. Intuitively, this scheme is very simple
72 scheme, a change in the number of targets causes nearly all keys to be
86 When using a Flow-Table based scheme to handle flow distribution/load
106 signatures and target values. This doesn't allow this scheme to scale to
132 scheme: given an input key the lookup operation is reduced to hashing
/f-stack/app/nginx-1.16.1/conf/
H A Duwsgi_params11 uwsgi_param REQUEST_SCHEME $scheme;
H A Dscgi_params11 scgi_param REQUEST_SCHEME $scheme;
H A Dfastcgi.conf13 fastcgi_param REQUEST_SCHEME $scheme;
H A Dfastcgi_params12 fastcgi_param REQUEST_SCHEME $scheme;
/f-stack/freebsd/contrib/device-tree/Bindings/mfd/
H A Dqcom,spmi-pmic.txt4 PMICs. These PMICs use a QPNP scheme through SPMI interface.
5 QPNP is effectively a partitioning scheme for dividing the SPMI extended
/f-stack/freebsd/arm/conf/
H A Dstd.armv730 options GEOM_PART_BSD # BSD partition scheme
31 options GEOM_PART_MBR # MBR partition scheme
H A Dstd.armv630 options GEOM_PART_BSD # BSD partition scheme
31 options GEOM_PART_MBR # MBR partition scheme
/f-stack/freebsd/contrib/device-tree/Bindings/power/reset/
H A Dqnap-poweroff.txt8 Synology NAS devices use a similar scheme, but a different baud rate,
/f-stack/freebsd/contrib/device-tree/Bindings/arm/ti/
H A Dk3.txt5 shall follow the following scheme:
/f-stack/freebsd/contrib/openzfs/cmd/zed/agents/
H A Dzfs_retire.c317 char *scheme; in zfs_retire_recv() local
442 &scheme) != 0) in zfs_retire_recv()
445 if (strcmp(scheme, FM_FMRI_SCHEME_ZFS) != 0) in zfs_retire_recv()
/f-stack/freebsd/contrib/device-tree/Bindings/firmware/
H A Dnvidia,tegra186-bpmp.txt53 services. Put another way, the numbering scheme for I2C buses is distinct from
54 the numbering scheme for any other service the BPMP may provide (e.g. a future
/f-stack/freebsd/contrib/device-tree/Bindings/sound/
H A Dti,tas5086.txt25 sequence, otherwise the default Low-Z scheme is used.
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dkeep_alive.rst82 Keep-Alive/'Liveliness' conceptual scheme. As mentioned in the
86 The Keep-Alive/'Liveliness' conceptual scheme:
H A Dqos_metering.rst16 A policing scheme can be applied before writing the packets to the TX port by dropping or
120 To set up the policing scheme as desired, it is necessary to modify the main.h source file,
/f-stack/freebsd/contrib/device-tree/Bindings/mailbox/
H A Dqcom-ipcc.yaml15 addressing scheme called protocol, client and signal. For example, consider an
/f-stack/freebsd/contrib/device-tree/Bindings/net/
H A Dcavium-pip.txt4 devices. The devices have a two level grouping scheme. There may be
/f-stack/freebsd/contrib/device-tree/Bindings/interrupt-controller/
H A Dbrcm,bcm2835-armctrl-ic.txt4 72 interrupt sources using a 2-level register scheme. The interrupt
/f-stack/dpdk/doc/guides/eventdevs/
H A Ddlb.rst178 DLB uses a hardware credit scheme to prevent software from overflowing hardware
238 credit scheme on top of the hardware credit scheme in order to comply with
241 The DLB's hardware scheme is local to a queue/pipeline stage: a port spends a
245 In the software credit scheme, a credit is consumed when a new (.op =
/f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/
H A Dingenic,pinctrl.txt10 naming scheme "PxN" where x is a character identifying the GPIO port with

1234