aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/sched-migration.py
diff options
context:
space:
mode:
authorPaolo Abeni <[email protected]>2022-05-02 10:30:36 +0200
committerPaolo Abeni <[email protected]>2022-05-02 10:30:36 +0200
commit0f0c0452bbd46d713eeb8968f5f40ccc257f85eb (patch)
treeaac9db6af288e593edb6fb6355c6c9d6a1e5dbc1 /tools/perf/scripts/python/sched-migration.py
parent6e28f56c0d1d976a4940d13d7f27e446ce65cd0a (diff)
parentb11ebf2ca2c118ed8767fc37a151d5c70844617d (diff)
Merge branch 'devices-always-netif_f_lltx'
Peilin Ye says: ==================== devices always NETIF_F_LLTX v1: https://lore.kernel.org/netdev/[email protected]/ change since v1: - deleted "depends on patch..." in [1/2]'s commit message This patchset depends on these fixes [1], which has been merged into net-next. Since o_seqno is now atomic_t, we can always turn on NETIF_F_LLTX for [IP6]GRE[TAP] devices, since we no longer need the TX lock (&txq->_xmit_lock). We could probably do the same thing to [IP6]ERSPAN devices as well, but I'm not familiar with them yet. For example, ERSPAN devices are initialized as |= GRE_FEATURES in erspan_tunnel_init(), but I don't see IP6ERSPAN devices being initialized as |= GRE6_FEATURES. Where should we initialize IP6ERSPAN devices' ->features? Please suggest if I'm missing something, thanks! [1] https://lore.kernel.org/netdev/[email protected]/ ==================== Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Paolo Abeni <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/sched-migration.py')
0 files changed, 0 insertions, 0 deletions