1. 21 Oct, 2021 15 commits
  2. 28 Sep, 2021 1 commit
  3. 27 Sep, 2021 8 commits
  4. 24 Sep, 2021 2 commits
  5. 23 Sep, 2021 9 commits
  6. 22 Sep, 2021 5 commits
    • David S. Miller's avatar
      Merge branch 'mlxsw-trap-adjacency' · 428168f9
      David S. Miller authored
      Ido Schimmel says:
      
      ====================
      mlxsw: Alter trap adjacency entry allocation scheme
      
      In commit 0c3cbbf9 ("mlxsw: Add specific trap for packets routed via
      invalid nexthops"), mlxsw started allocating a new adjacency entry
      during driver initialization, to trap packets routed via invalid
      nexthops.
      
      This behavior was later altered in commit 983db619 ("mlxsw:
      spectrum_router: Allocate discard adjacency entry when needed") to only
      allocate the entry upon the first route that requires it. The motivation
      for the change is explained in the commit message.
      
      The problem with the current behavior is that the entry shows up as a
      "leak" in a new BPF resource monitoring tool [1]. This is caused by the
      asymmetry of the allocation/free scheme. While the entry is allocated
      upon the first route that requires it, it is only freed during
      de-initialization of the driver.
      
      Instead, this patchset tracks the number of active nexthop groups and
      allocates the adjacency entry upon the creation of the first group. The
      entry is freed when the number of active groups reaches zero.
      
      Patch #1 adds the new entry.
      
      Patch #2 converts mlxsw to start using the new entry and removes the old
      one.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      428168f9
    • Ido Schimmel's avatar
      mlxsw: spectrum_router: Start using new trap adjacency entry · e3a3aae7
      Ido Schimmel authored
      Start using the trap adjacency entry that was added in the previous
      patch and remove the existing one which is no longer needed.
      
      Note that the name of the old entry was inaccurate as the entry did not
      discard packets, but trapped them.
      Signed-off-by: default avatarIdo Schimmel <idosch@nvidia.com>
      Reviewed-by: default avatarJiri Pirko <jiri@nvidia.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e3a3aae7
    • Ido Schimmel's avatar
      mlxsw: spectrum_router: Add trap adjacency entry upon first nexthop group · 4bdf80bc
      Ido Schimmel authored
      In commit 0c3cbbf9 ("mlxsw: Add specific trap for packets routed via
      invalid nexthops"), mlxsw started allocating a new adjacency entry
      during driver initialization, to trap packets routed via invalid
      nexthops.
      
      This behavior was later altered in commit 983db619 ("mlxsw:
      spectrum_router: Allocate discard adjacency entry when needed") to only
      allocate the entry upon the first route that requires it. The motivation
      for the change is explained in the commit message.
      
      The problem with the current behavior is that the entry shows up as a
      "leak" in a new BPF resource monitoring tool [1]. This is caused by the
      asymmetry of the allocation/free scheme. While the entry is allocated
      upon the first route that requires it, it is only freed during
      de-initialization of the driver.
      
      Instead, track the number of active nexthop groups and allocate the
      adjacency entry upon the creation of the first group. Free it when the
      number of active groups reaches zero.
      
      The next patch will convert mlxsw to start using the new entry and
      remove the old one.
      
      [1] https://github.com/Mellanox/mlxsw/tree/master/Debugging/libbpf-tools/resmonSigned-off-by: default avatarIdo Schimmel <idosch@nvidia.com>
      Reviewed-by: default avatarJiri Pirko <jiri@nvidia.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      4bdf80bc
    • M Chetan Kumar's avatar
      net: wwan: iosm: fw flashing and cd improvements · 8bea96ef
      M Chetan Kumar authored
      1> Function comments moved to .c file.
      2> Use literals in return to improve readability.
      3> Do error handling check instead of success check.
      4> Redundant ret assignment removed.
      Signed-off-by: default avatarM Chetan Kumar <m.chetan.kumar@linux.intel.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      8bea96ef
    • Li RongQing's avatar
      skbuff: pass the result of data ksize to __build_skb_around · a5df6333
      Li RongQing authored
      Avoid to call ksize again in __build_skb_around by passing
      the result of data ksize to __build_skb_around
      
      nginx stress test shows this change can reduce ksize cpu usage,
      and give a little performance boost
      Signed-off-by: default avatarLi RongQing <lirongqing@baidu.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      a5df6333