| /f-stack/freebsd/contrib/openzfs/tests/test-runner/bin/ |
| H A D | zts-report.py.in | 130 summary = { variable
301 summary['total'] += 1
303 summary['passed'] += 1
309 summary['logfile'] = m.group(1)
319 if summary['total'] == 0:
321 print("Log directory: %s" % summary['logfile'])
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | member_lib.rst | 25 operations) in this set-summary is much faster than checking it for the
36 traffic monitoring. A set-summary is useful for applications who need to
87 set-summary schemes with and without false negative probability.
238 set-summary. It is worth noting that the set-summary still has false positive
274 Set-summary Create
285 …nly used for certain type of set-summary, or which have a slightly different meaning for different…
303 Set-summary Element Insertion
320 Set-summary Element Lookup
340 set-summary structure for multiple matches. It
360 set-summary structure. The arguments of the
[all …]
|
| /f-stack/app/redis-5.0.5/deps/lua/ |
| H A D | README | 4 See HISTORY for a summary of changes since the last released version.
13 For an executive summary, see http://www.lua.org/about.html .
|
| /f-stack/app/redis-5.0.5/src/ |
| H A D | help.h | 27 char *summary; member
|
| /f-stack/app/redis-5.0.5/deps/jemalloc/ |
| H A D | README | 18 The ChangeLog file contains a brief summary of changes for each release.
|
| /f-stack/app/redis-5.0.5/deps/lua/test/ |
| H A D | README | 5 Here is a one-line summary of each program:
|
| /f-stack/freebsd/contrib/openzfs/tests/ |
| H A D | README.md | 66 summary.
117 end of each test, and a results summary is printed at the end of the run. The
118 results summary includes the location of the complete logs, which is logged in
|
| /f-stack/app/nginx-1.16.1/ |
| H A D | configure | 116 . auto/summary
|
| /f-stack/dpdk/devtools/ |
| H A D | check-includes.sh | 44 -s show summary
|
| /f-stack/app/nginx-1.16.1/auto/ |
| H A D | summary | 7 echo "Configuration summary"
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mfd/ |
| H A D | qcom-pm8xxx.txt | 30 has generated an interrupt (summary interrupt). The
|
| /f-stack/freebsd/contrib/device-tree/Bindings/spmi/ |
| H A D | qcom,spmi-pmic-arb.txt | 36 "periph_irq" - summary interrupt for PMIC peripherals
|
| /f-stack/freebsd/contrib/device-tree/Bindings/ |
| H A D | ABI.rst | 8 summary document:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/ |
| H A D | qcom,sm8250-pinctrl.yaml | 31 description: Specifies the TLMM summary IRQ
|
| H A D | qcom,ipq6018-pinctrl.yaml | 24 description: Specifies the TLMM summary IRQ
|
| H A D | mediatek,mt6779-pinctrl.yaml | 57 Specifies the summary IRQ.
|
| H A D | qcom,mdm9615-pinctrl.txt | 19 Definition: should specify the TLMM summary IRQ.
|
| H A D | qcom,apq8084-pinctrl.txt | 19 Definition: should specify the TLMM summary IRQ.
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | enetc.rst | 19 Contents summary
|
| H A D | dpaa2.rst | 20 Contents summary
194 is provided along with a summary of the kinds of operations the object
195 supports and a summary of key resources of the object (MMIO regions
|
| H A D | pfe.rst | 19 Contents summary
|
| /f-stack/dpdk/doc/guides/contributing/ |
| H A D | patches.rst | 196 The first, summary, line of the git commit message becomes the subject line of the patch email.
197 Here are some guidelines for the summary line:
199 * The summary line must capture the area and the impact of the change.
201 * The summary line should be around 50 characters.
203 * The summary line should be lowercase apart from acronyms.
584 follows the kernel usage of the tags. A short summary of the meanings of each
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | eventdev_pipeline.rst | 70 At runtime the eventdev pipeline application prints out a summary of the
|
| /f-stack/dpdk/lib/ |
| H A D | meson.build | 59 enabled_libs = [] # used to print summary at the end
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mmc/ |
| H A D | ti-omap-hsmmc.txt | 110 In summary:
|