19/06/2020 12:53, Anatoly Burakov:
> Since 20.05, l3fwd-power has become much more stringent about
> whether it allows initialization without initializing the
> librte_power library with it. This means that while previously
> the app could have been used to test RX interrupts functionality
> even if the app itself was in a half-working state, it is now
> no longer possible to do so.
>
> To address this use case, we're adding an interrupt-only mode
> that does not rely on librte_power or telemetry. This enables
> using l3fwd-power in environments where librte_power is not
> expected to work (such as inside a VM or on non-IA
> architectures). The RX/TX path is basically copy paste from
> legacy RX/TX path but with librte_power bits taken out.
>
> There seem to be two opposing schools of thought on whether we
> should have more or less examples. This patchset goes in the
> "less" direction where we add a new mode to an existing app,
> rather than creating a new one like it could be argued it
> deserves.
>
> v3:
> - Added log messages for autodetect
> - Fixed wrong comment in patch 7
>
> v2:
> - Add API to probe support for a specific power env
> - Add autodetection for the default mode
> - Add ability to request legacy mode specifically
> - Fix some code style issues
>
> Anatoly Burakov (7):
> l3fwd-power: disable interrupts by default
> l3fwd-power: only allow supported power library envs
> l3fwd-power: code style and flow fixes
> l3fwd-power: add support for requesting legacy mode
> l3fwd-power: add interrupt-only mode
> power: add API to probe support for a specific env
> l3fwd-power: add auto-selection of default mode
Applied with following titles:
examples/l3fwd-power: disable interrupts by default
examples/l3fwd-power: allow only supported environments
examples/l3fwd-power: fix style and control flow
examples/l3fwd-power: add legacy mode option
examples/l3fwd-power: add interrupt-only mode
power: add environment capability probing
examples/l3fwd-power: select default mode automatically
