Lines Matching refs:or

21 …creating new files, the style should be consistent within each file in a given directory or module.
113 Do not ``#define`` or declare names except with the standard DPDK prefix: ``RTE_``.
118 The expansions of expression-like macros are either a single token or have outer parentheses.
156   or platform-specific way, then create a file for each OS or platform
163 * When code is conditionally compiled using ``#ifdef`` or ``#if``, a comment may be added following…
164 …``#endif`` or ``#else`` to permit the reader to easily discern where conditionally compiled code r…
165 … used only for (subjectively) long regions, regions greater than 20 lines, or where a series of ne…
166 …ases where code is conditionally not compiled for the purposes of lint(1), or other tools, even th…
167 * The comment should be separated from the ``#endif`` or ``#else`` by a single space.
169 * The comment for ``#endif`` should match the expression used in the corresponding ``#if`` or ``#if…
170 …d match the inverse of the expression(s) used in the preceding ``#if`` and/or ``#elif`` statements.
181  /* A large region here, or other conditional code. */
187  /* Yet another large region here, or other conditional code. */
196 the target platform, or runtime environment.
287 * Do not use uppercase letters - either in the form of ALL_UPPERCASE, or CamelCase - in variable na…
311 * Major structures should be declared at the top of the file in which they are used, or in separate…
344 This should be used in all data-path code, when there are several consumer and/or producers to avoi…
350 'master / slave' (or 'slave' independent of 'master') and 'blacklist /
365 with an existing (as of 2020) hardware or protocol
397 for example, you need to know if the typedef is the structure itself, as shown above, or a pointer …
400 The header that defines the typedef must be included before the header that uses it, or by the head…
401 or there must be a back-door mechanism for obtaining the typedef.
408 Avoid typedefs ending in ``_t``, except as specified in Standard C or by POSIX.
443 …ion as to whether the second line of the control statement forms part of the statement body or not.
471 * Do not add whitespace or a blank line at the end of a file.
478 * Do not use braces (``{`` and ``}``) for control statements with zero or just a single statement, …
527 * No spaces after ``(`` or ``[`` or preceding the ``]`` or ``)`` characters.
540 * Do not use parentheses unless they are required for precedence or unless the statement is confusi…
546 Exits should be 0 on success, or 1 on failure.
598 * Do not use uppercase letters - either in the form of ALL_UPPERCASE, or CamelCase - in function na…
662 …Use NULL instead of ``(type *)0`` or ``(type *)NULL``, except where the compiler does not know the…
681 * Functions which create objects, or allocate memory, should return pointer types, and NULL on erro…
683 * Functions which work on bursts of packets, such as RX-like or TX-like functions, should return th…
687 …Note, however, to allow consistency across functions returning integer or pointer types, the previ…
734 …cal zone (called often or in a data path) the code can use the ``likely()`` and ``unlikely()`` mac…
735 …er builtin and allow the developer to indicate if the branch is likely to be taken or not. Example:
746 …and only when there is a clearly preferred path, or a measured performance increase gained from do…
753 …ould be inlined should to be declared as ``static inline`` and can be defined in a .c or a .h file.
801 useful for enabling debug output without recompilation. To enable or disable
827 In addition to the above logging topic, any PMD or library can further split
833 Each PMD, library or component can create as many specializations as required.
872 either ``lib`` directory or a ``driver`` subdirectory.
903 	Used to optionally compile a library, based on its dependencies or
941 	``dependency()`` or ``find_library()`` functions. Before returning
986 	If a library's .so or .a file differs from that given in the directory
1016 	twice with suitable parameters for each of shared or static library
1097 * Lists of files or components must be alphabetical unless doing so would cause errors.
1099 * Two formats are supported for lists of files or list of components:
1101 …* For a small number of list entries, generally 3 or fewer, all elements may be put on a single li…
1106      In this case, the opening brace, or ``files`` function call must be on a line on its own,