| /dpdk/doc/guides/rel_notes/ |
| H A D | release_1_8.rst | 14 * Support for registration of link status change callbacks with link bonding devices.
16 …* Support for slaves devices which do not support link status change interrupts in the link bond…
|
| H A D | release_2_0.rst | 39 * Support for registration of link status change callbacks with link bonding devices.
41 …* Support for slaves devices which do not support link status change interrupts in the link bond…
|
| H A D | release_22_07.rst | 126 * sample: Add a short 1-2 sentence description of the API change
142 * sample: Add a short 1-2 sentence description of the ABI change
152 * No ABI change that would break compatibility with 21.11.
|
| H A D | deprecation.rst | 25 This change will not introduce any performance degradation.
33 20.08 onwards. This change will not introduce any performance degradation.
48 in the header will not be considered as ABI anymore. This change is inspired
|
| /dpdk/doc/guides/contributing/ |
| H A D | abi_policy.rst | 36 ABI change.
93 The ABI may then change multiple times, without warning, between the last major
96 sonames do not change.
119 The ABI may still change after the declaration of a major ABI version, that is
139 for that component must acknowledge the ABI change instead.
143 the need for the ABI change, is also mandatory.
198 which was previously supported, should be treated as an ABI change, and
371 and is unlikely to change.
379 Should an ABI change, usually due to a direct change to the API's signature,
|
| H A D | abi_versioning.rst | 39 An ABI version change to a given library, especially in core libraries such as
43 obvious change to the dependent library's API, even though the library's ABI
71 When an ABI change is made between major ABI versions to a given library, a new
74 library's soname and filename however do not change, e.g. ``libacl.so.21``, as
130 arguments. Occasionally that function may need to change to accommodate new
|
| H A D | stable.rst | 117 * How intrusive is the code change?
118 * What is the scope of the code change?
|
| H A D | patches.rst | 191 A good way of thinking about whether a patch should be split is to consider whether the change coul…
203 * The summary line must capture the area and the impact of the change.
237 * When the change is obvious the body can be blank, apart from the signoff.
523 If the patches are a change to existing files then you should send them TO the maintainer(s) and CC…
719 * A driver change must include documentation
729 * The application change must include documentation in the relevant .rst files
|
| /dpdk/drivers/net/qede/ |
| H A D | qede_main.c | 186 uint8_t change = 0; in qede_vf_task() local
189 ecore_vf_read_bulletin(p_hwfn, &change); in qede_vf_task()
190 if (change) in qede_vf_task()
510 uint8_t change = 0; in qed_fill_link() local
522 ecore_vf_read_bulletin(hwfn, &change); in qed_fill_link()
|
| /dpdk/drivers/net/vmxnet3/base/ |
| H A D | README | 9 In which, upt1_defs.h and vmxnet3_defs.h is introduced without any change.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | power_man.rst | 160 change thresholds for a given system. The thresholds will differ from
189 * **Detect empty poll state change**: empty poll state change detection algorithm then take action.
201 Existing power management mechanisms require developers to change application
202 design or change code to make use of it. The PMD power management API provides a
|
| H A D | link_bonding_poll_mode_drv_lib.rst | 215 Link bonding devices support the registration of a link status change callback,
218 device which has 3 slaves, the link status will change to up when one slave
219 becomes active or change to down when all slaves become inactive. There is no
225 status change interrupts, this is achieved by polling the devices link status at
452 checked for a change in the devices link status
|
| /dpdk/doc/guides/nics/ |
| H A D | atlantic.rst | 27 - MACSEC PMD API is considered as experimental and is subject to change/removal in next DPDK releas…
|
| H A D | ngbe.rst | 47 One may leverage EAL option "--log-level" to change default levels
|
| H A D | netvsc.rst | 31 * The Hyper-V driver does not use or support interrupts. Link state change
32 callback is done via change events in the packet ring.
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | link_status_intr.rst | 113 Configuring lsc to 0 (the default) disables the generation of any link status change interrupts in …
116 Configuring lsc to non-zero enables the generation of link status change interrupts in kernel space
117 when a link status change is present and calls the user space callbacks registered by the applicati…
|
| H A D | vm_power_management.rst | 12 may change over time. In addition, operating systems on Virtual Machines
24 - **Performing the change in frequency**
28 - **The handling of VM application requests to change frequency.**
32 performs the frequency change.
530 Allows the user to change the virtual machine name
575 To change the frequency of an lcore, use a ``set_cpu_freq`` command similar
582 where, ``{core_num}`` is the lcore and channel to change frequency by
|
| H A D | ethtool.rst | 9 its use to query and change Ethernet card parameters. The sample
|
| /dpdk/license/ |
| H A D | gpl-2.0.txt | 12 freedom to share and change it. By contrast, the GNU General Public
13 License is intended to guarantee your freedom to share and change free
25 if you want it, that you can change the software or use pieces of it
96 stating that you changed the files and the date of any change.
286 free software which everyone can redistribute and change under these terms.
|
| H A D | lgpl-2.1.txt | 16 freedom to share and change it. By contrast, the GNU General Public
17 Licenses are intended to guarantee your freedom to share and change
31 it if you want it; that you can change the software and use pieces of
170 stating that you changed the files and the date of any change.
217 that version instead if you wish.) Do not make any other change in
220 Once this change is made in a given copy, it is irreversible for
464 everyone can redistribute and change. You can do so by permitting
|
| /dpdk/devtools/ |
| H A D | checkpatches.sh | 12 VALIDATE_NEW_API=$(dirname $(readlink -f $0))/check-symbol-change.sh
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | build_sample_apps.rst | 44 change between platforms and should be determined beforehand. The corelist is
154 …The logical core layout can change between different board layouts and should be checked before se…
|
| /dpdk/doc/guides/vdpadevs/ |
| H A D | mlx5.rst | 65 dynamic delay change steps according to this value. Default value is 1us.
|
| H A D | sfc.rst | 82 One may leverage EAL option "--log-level" to change default levels
|
| /dpdk/doc/guides/howto/ |
| H A D | virtio_user_for_container_networking.rst | 43 in DPDK's ether layer. And to minimize the change, we reuse already-existing
|