• Jakub Kicinski's avatar
    nfp: default to chained metadata prepend format · 64a919a9
    Jakub Kicinski authored
    ABI 4.x introduced the chained metadata format and made it the
    only one possible.  There are cases, however, where the old
    format is preferred - mostly to make interoperation with VFs
    using ABI 3.x easier for the datapath.  In ABI 5.x we allowed
    for more flexibility by selecting the metadata format based
    on capabilities.  The default was left to non-chained.
    
    In case of fallback traffic, there is no capability telling the
    driver there may be chained metadata.  With a very stripped-
    -down FW the default old metadata format would be selected
    making the driver drop all fallback traffic.
    
    This patch changes the default selection in the driver. It
    should not hurt with old firmwares, because if they don't
    advertise RSS they will not produce metadata anyway.  New
    firmwares advertising ABI 5.x, however, can depend on the
    driver defaulting to chained format.
    
    Fixes: f9380629 ("nfp: advertise support for NFD ABI 0.5")
    Suggested-by: default avatarMichael Rapson <michael.rapson@netronome.com>
    Signed-off-by: default avatarJakub Kicinski <jakub.kicinski@netronome.com>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    64a919a9
nfp_net_common.c 97.3 KB