1. 27 3月, 2020 12 次提交
  2. 18 3月, 2020 13 次提交
  3. 12 3月, 2020 2 次提交
  4. 13 2月, 2020 1 次提交
    • D
      iwlwifi: mvm: Do not require PHY_SKU NVM section for 3168 devices · a9149d24
      Dan Moulding 提交于
      The logic for checking required NVM sections was recently fixed in
      commit b3f20e09 ("iwlwifi: mvm: fix NVM check for 3168
      devices"). However, with that fixed the else is now taken for 3168
      devices and within the else clause there is a mandatory check for the
      PHY_SKU section. This causes the parsing to fail for 3168 devices.
      
      The PHY_SKU section is really only mandatory for the IWL_NVM_EXT
      layout (the phy_sku parameter of iwl_parse_nvm_data is only used when
      the NVM type is IWL_NVM_EXT). So this changes the PHY_SKU section
      check so that it's only mandatory for IWL_NVM_EXT.
      
      Fixes: b3f20e09 ("iwlwifi: mvm: fix NVM check for 3168 devices")
      Signed-off-by: NDan Moulding <dmoulding@me.com>
      Signed-off-by: NKalle Valo <kvalo@codeaurora.org>
      a9149d24
  5. 04 2月, 2020 8 次提交
  6. 01 2月, 2020 2 次提交
  7. 26 1月, 2020 1 次提交
  8. 23 1月, 2020 1 次提交
    • M
      net: Fix packet reordering caused by GRO and listified RX cooperation · c8079432
      Maxim Mikityanskiy 提交于
      Commit 323ebb61 ("net: use listified RX for handling GRO_NORMAL
      skbs") introduces batching of GRO_NORMAL packets in napi_frags_finish,
      and commit 6570bc79 ("net: core: use listified Rx for GRO_NORMAL in
      napi_gro_receive()") adds the same to napi_skb_finish. However,
      dev_gro_receive (that is called just before napi_{frags,skb}_finish) can
      also pass skbs to the networking stack: e.g., when the GRO session is
      flushed, napi_gro_complete is called, which passes pp directly to
      netif_receive_skb_internal, skipping napi->rx_list. It means that the
      packet stored in pp will be handled by the stack earlier than the
      packets that arrived before, but are still waiting in napi->rx_list. It
      leads to TCP reorderings that can be observed in the TCPOFOQueue counter
      in netstat.
      
      This commit fixes the reordering issue by making napi_gro_complete also
      use napi->rx_list, so that all packets going through GRO will keep their
      order. In order to keep napi_gro_flush working properly, gro_normal_list
      calls are moved after the flush to clear napi->rx_list.
      
      iwlwifi calls napi_gro_flush directly and does the same thing that is
      done by gro_normal_list, so the same change is applied there:
      napi_gro_flush is moved to be before the flush of napi->rx_list.
      
      A few other drivers also use napi_gro_flush (brocade/bna/bnad.c,
      cortina/gemini.c, hisilicon/hns3/hns3_enet.c). The first two also use
      napi_complete_done afterwards, which performs the gro_normal_list flush,
      so they are fine. The latter calls napi_gro_receive right after
      napi_gro_flush, so it can end up with non-empty napi->rx_list anyway.
      
      Fixes: 323ebb61 ("net: use listified RX for handling GRO_NORMAL skbs")
      Signed-off-by: NMaxim Mikityanskiy <maximmi@mellanox.com>
      Cc: Alexander Lobakin <alobakin@dlink.ru>
      Cc: Edward Cree <ecree@solarflare.com>
      Acked-by: NAlexander Lobakin <alobakin@dlink.ru>
      Acked-by: NSaeed Mahameed <saeedm@mellanox.com>
      Acked-by: NEdward Cree <ecree@solarflare.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c8079432