1. 09 12月, 2015 4 次提交
  2. 19 11月, 2015 2 次提交
    • E
      net: provide generic busy polling to all NAPI drivers · 93d05d4a
      Eric Dumazet 提交于
      NAPI drivers no longer need to observe a particular protocol
      to benefit from busy polling (CONFIG_NET_RX_BUSY_POLL=y)
      
      napi_hash_add() and napi_hash_del() are automatically called
      from core networking stack, respectively from
      netif_napi_add() and netif_napi_del()
      
      This patch depends on free_netdev() and netif_napi_del() being
      called from process context, which seems to be the norm.
      
      Drivers might still prefer to call napi_hash_del() on their
      own, since they might combine all the rcu grace periods into
      a single one, knowing their NAPI structures lifetime, while
      core networking stack has no idea of a possible combining.
      
      Once this patch proves to not bring serious regressions,
      we will cleanup drivers to either remove napi_hash_del()
      or provide appropriate rcu grace periods combining.
      Signed-off-by: NEric Dumazet <edumazet@google.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      93d05d4a
    • E
      net: move skb_mark_napi_id() into core networking stack · 93f93a44
      Eric Dumazet 提交于
      We would like to automatically provide busy polling support
      to all NAPI drivers, without them having to implement anything.
      
      skb_mark_napi_id() can be called from napi_gro_receive() and
      napi_get_frags().
      
      Few drivers are still calling skb_mark_napi_id() because
      they use netif_receive_skb(). They should eventually call
      napi_gro_receive() instead. I will leave this to drivers
      maintainers.
      Signed-off-by: NEric Dumazet <edumazet@google.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      93f93a44
  3. 22 10月, 2015 9 次提交
  4. 11 10月, 2015 1 次提交
  5. 05 10月, 2015 4 次提交
  6. 04 10月, 2015 1 次提交
  7. 29 9月, 2015 1 次提交
  8. 18 9月, 2015 1 次提交
  9. 10 9月, 2015 3 次提交
  10. 07 9月, 2015 1 次提交
    • F
      cxgb4: fix usage of uninitialized variable · 46cdc9be
      françois romieu 提交于
      drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c: In function ‘init_one’:
      drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:4579:8: warning: ‘chip’ may be used uninitialized in this function [-Wmaybe-uninitialized]
         chip |= CHELSIO_CHIP_CODE(CHELSIO_T4, pl_rev);
              ^
      drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:4571:11: note: ‘chip’ was declared here
        int ver, chip;
                 ^
      
      Fixes: d86bd29e ("cxgb4/cxgb4vf: read the correct bits of PL Who Am I register")
      Signed-off-by: NFrancois Romieu <romieu@fr.zoreil.com>
      Cc: Hariprasad Shenai <hariprasad@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      46cdc9be
  11. 29 8月, 2015 1 次提交
  12. 19 8月, 2015 1 次提交
  13. 14 8月, 2015 1 次提交
  14. 13 8月, 2015 4 次提交
  15. 11 8月, 2015 2 次提交
  16. 04 8月, 2015 4 次提交