Searched refs:collisions (Results 1 – 19 of 19) sorted by relevance
62 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 071 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 080 TX errors 8 dropped 8 overruns 0 carrier 8 collisions 089 TX errors 7 dropped 0 overruns 0 carrier 0 collisions 098 TX errors 7 dropped 7 overruns 0 carrier 0 collisions 0
167 int "number of bits reserved to handle collisions between hash numbers"171 The maximum number of hash collisions needs to be well sized depending
42 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 052 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
84 at 0x10000. Even given collisions, this is probably tolerable, as we
124 that some collisions between key's hashes could occur if a big number of127 ZMS backend can handle :math:`2^n` maximum collisions where n is defined by
240 `STM32H7B3I_DK board schematics`_ for possible collisions if using that connector.
108 To avoid collisions with user defined descriptors, the standard descriptors were allotted
64 PR("Collisions : %u\n", data->collisions); in print_eth_stats()
209 * Spec states rules for how to handle/resolve collisions when they happen
66 arbitration phase. During the arbitration phase, write collisions are allowed.
622 net_stats_t collisions; member
1215 Rule A.3: Macro name collisions1222 protected to avoid name collisions with other implementations. In particular, they must not be1234 …Finally, this rule applies to inter-module name collisions as well: in that case both modules, pri…1244 possible to patch the macro implementation in each module to avoid collisions.
109 * Makefile: Changed outdir into board-specific directory to avoid build collisions.
205 * Added full virtual addresses support with the collisions resolution. The
803 * Changed eth_stm32 to use phy APIs to access the phy to avoid collisions when multitasking.
362 - Divide IDs into namespaces and allocate IDs on demand from application to handle collisions
5 # before using them to avoid name-space collisions.
1304 be used in resolving collisions.
871 20 to 500ms. This option reduces the probability of collisions when multiple nodes publish
