Home
last modified time | relevance | path

Searched refs:log (Results 1 – 25 of 80) sorted by relevance

1234

/dpdk/devtools/
H A Dcheck-git-log.sh14 Check commit log formatting.
50 commits=$(git log --format='%h' --reverse $range)
51 headlines=$(git log --format='%s' --reverse $range)
52 bodylines=$(git log --format='%b' --reverse $range)
76 headline=$(git log --format='%s' -1 $commit)
160 body=$(git log --format='%b' -1 $commit)
163 git log --format='\t%s' -1 $commit
170 body=$(git log --format='%b' -1 $commit)
173 git log --format='\t%s' -1 $commit
181 git log --format='\t%s' -1 $fix
[all …]
H A Dgit-log-fixes.sh62 git log --format='%b' -1 $1 |
90 if git log --format='%b' -1 $1 | grep -qi '^Cc: *[email protected]' ; then
100 if git log --format='%b' -1 $1 | grep -qi '^Fixes: *' ; then
107 git log --oneline --reverse $range |
/dpdk/doc/guides/vdpadevs/
H A Dsfc.rst82 One may leverage EAL option "--log-level" to change default levels
83 for the log types supported by the driver. The option is used with
88 Depending on the choice of the expression, the given log level may
89 be used either for some specific log type or for a subset of types.
91 SFC vDPA PMD provides the following log types available for control:
99 Matches a subset of per-port log types registered during runtime.
106 The format of the log is consumed by the netlogdecode cross-platform
H A Dfeatures_overview.rst60 log all
61 Device can log all write descriptors (live migration).
84 proto log shmfd
85 Guest support setting log base.
/dpdk/drivers/net/hns3/
H A Dhns3_rss.h60 int log = 0; in rss_ilog2() local
64 log++; in rss_ilog2()
67 return log; in rss_ilog2()
/dpdk/doc/guides/vdpadevs/features/
H A Dmlx5.ini12 log all = Y
19 proto log shmfd = Y
H A Ddefault.ini27 log all =
35 proto log shmfd =
/dpdk/doc/guides/nics/
H A Dngbe.rst47 One may leverage EAL option "--log-level" to change default levels
48 for the log types supported by the driver. The option is used with
51 NGBE PMD provides the following log types available for control:
H A Dtxgbe.rst73 One may leverage EAL option "--log-level" to change default levels
74 for the log types supported by the driver. The option is used with
77 TXGBE PMD provides the following log types available for control:
90 Supply ``--log-level=pmd.net.txgbe.bp:debug`` to view messages.
H A Dsfc_efx.rst503 One may leverage EAL option "--log-level" to change default levels
504 for the log types supported by the driver. The option is used with
509 Depending on the choice of the expression, the given log level may
510 be used either for some specific log type or for a subset of types.
512 SFC EFX PMD provides the following log types available for control:
520 Matches a subset of per-port log types registered during runtime.
527 The format of the log is consumed by the Solarflare netlogdecode
/dpdk/doc/guides/howto/
H A Drte_flow.rst85 Terminal 1: output log::
104 Terminal 1: output log::
185 Terminal 1: output log::
207 Terminal 1: output log::
279 Terminal 1: output log::
301 Terminal 1: output log::
/dpdk/lib/member/
H A Drte_member_vbf.c64 log(fp_one_bf)) / in rte_member_create_vbf()
65 log(1.0 / (pow(2.0, log(2.0))))); in rte_member_create_vbf()
70 ss->num_hashes = (uint32_t)(log(2.0) * bits / num_keys_per_bf); in rte_member_create_vbf()
/dpdk/doc/guides/regexdevs/
H A Dcn9k.rst46 | # | Component | EAL log command |
48 | 1 | REE | --log-level='pmd\.regex\.cn9k,8' |
/dpdk/drivers/net/qede/base/
H A Dbcm_osal.c72 u32 log = 0; in qede_osal_log2() local
75 log++; in qede_osal_log2()
77 return log; in qede_osal_log2()
/dpdk/doc/guides/rawdevs/
H A Ddpaa2_cmdif.rst49 ./your_cmdif_application <EAL args> --log-level=pmd.raw.dpaa2.cmdif,<level>
51 Using ``pmd.raw.dpaa2.cmdif`` as log matching criteria, all Event PMD logs can be
H A Ddpaa2_qdma.rst53 ./your_qdma_application <EAL args> --log-level=pmd.raw.dpaa2.qdma,<level>
55 Using ``pmd.raw.dpaa2.qdma`` as log matching criteria, all Event PMD logs can be
/dpdk/doc/guides/eventdevs/
H A Ddpaa2.rst72 ./your_eventdev_application <EAL args> --log-level=pmd.event.dpaa2,<level>
74 Using ``eventdev.dpaa2`` as log matching criteria, all Event PMD logs can be
H A Dcnxk.rst193 | # | Component | EAL log command |
195 | 1 | SSO | --log-level='pmd\.event\.cnxk,8' |
197 | 2 | TIM | --log-level='pmd\.event\.cnxk\.timer,8' |
/dpdk/lib/node/
H A Dmeson.build16 'log.c',
/dpdk/doc/guides/mempool/
H A Dcnxk.rst73 | # | Component | EAL log command |
75 | 1 | NPA | --log-level='pmd\.mempool.cnxk,8' |
/dpdk/doc/guides/linux_gsg/
H A Deal_args.include.rst131 * ``--log-level <type:val>``
133 Specify log level for a specific component. For example::
135 --log-level lib.eal:debug
/dpdk/app/test-acl/
H A Dtest-acl.sh61 ${TACL_PATH} -l 0 -n 4 --log-level="acl,debug" \
/dpdk/doc/guides/prog_guide/
H A Dasan.rst52 …s enabled, because apply 9 bytes of memory but access the tenth byte, detailed error log as below::
81 …ause apply 9 bytes of memory but access the first byte after release, detailed error log as below::
/dpdk/doc/guides/cryptodevs/
H A Ddpaa_sec.rst122 ./your_crypto_application <EAL args> --log-level=pmd.crypto.dpaa:<level>
124 Using ``pmd.crypto.dpaa`` as log matching criteria, all Crypto PMD logs can be
H A Dqat.rst470 If you see the following warning in ``/var/log/messages`` it can be ignored:
675 They can be enabled using the log-level option (where 8=maximum log level) on
678 --log-level="pmd.qat.general,8"
679 --log-level="pmd.qat.dp,8"
680 --log-level="pmd.qat,8"
687 Also the dynamic global log level overrides both sets of trace, so e.g. no
690 --log-level="7" --log-level="pmd.qat.general,8"

1234