Searched refs:stable (Results 1 – 14 of 14) sorted by relevance
18 consumers of DPDK with a stable target on which to base applications or21 The primary characteristics of stable releases is that they attempt to23 compatibility with the initial release of the stable version.54 A stable release can be designated as an LTS release based on community59 https://git.dpdk.org/dpdk-stable where bugfixes will be backported to.72 For a list of the currently maintained stable/LTS branches please see73 the latest `stable roadmap <https://core.dpdk.org/roadmap/#stable>`_.95 Cc: stable@dpdk.org104 New features should not be backported to stable releases.108 stable maintainers are as follows:[all …]
19 stable
10 Only the main repositories (dpdk and dpdk-stable) of the core project12 If a stable branch is declared unmaintained (end of life),280 * For long and short term stable branches fixed,292 and `stable@dpdk.org <mailto:stable@dpdk.org>`_ accordingly.
48 **single ABI version**. In addition, the need to maintain a stable ABI for some121 DPDK versions being installed alongside each other. Both stable and160 The macro is used when a symbol matures to become part of the stable ABI, to428 In situations in which an ``experimental`` symbol has been stable for some time,429 and it becomes a candidate for promotion to the stable ABI. At this time, when471 When we promote the symbol to the stable ABI, we simply strip the
328 should also be CCed to the `stable@dpdk.org <https://mails.dpdk.org/listinfo/stable>`_330 In the commit message body the Cc: stable@dpdk.org should be inserted as follows::337 Cc: stable@dpdk.org341 For further information on stable contribution you can go to342 :doc:`Stable Contribution Guide <stable>`.556 for a stable release rather than mainline.557 In this case the patch(es) should be sent to ``stable@dpdk.org``,560 Given that there are multiple stable releases being maintained at the same time,
161 - In situations in which an ``experimental`` symbol has been stable for some364 Promotion to stable369 Ordinarily APIs marked as ``experimental`` will be promoted to the stable ABI375 and is without any prospect of becoming part of the stable API.
110 stable=$(stable_tag $id)112 [ "$stable" = "S" ] || [ "$fixes" = "F" ] || [ -n "$origins" ] || \123 printf '%s %7s %s %s %s (%s)\n' $version $id $stable $fixes "$headline" "$origver"
631 …<https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/pci/quirks.c?…680 …`commit <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/pc…
512 * vhost: Moved vDPA APIs from experimental to stable.547 subsequently moved ``rte_ipsec`` lib from experimental to stable.578 interfaces are considered stable as of DPDK 20.11.
240 * The soname for each stable ABI version should be just the ABI version major
110 The kernel version required is based on the oldest long term stable kernel available
69 T: git://dpdk.org/dpdk-stable
1321 The output value is the average queue size which gives a more stable view of the current congestion…
2622 testpmd> set bonding agg_mode (port_id) (bandwidth|count|stable)