1. 03 12月, 2015 11 次提交
  2. 02 12月, 2015 1 次提交
    • V
      hv_netvsc: rework link status change handling · 27a70af3
      Vitaly Kuznetsov 提交于
      There are several issues in hv_netvsc driver with regards to link status
      change handling:
      - RNDIS_STATUS_NETWORK_CHANGE results in calling userspace helper doing
        '/etc/init.d/network restart' and this is inappropriate and broken for
        many reasons.
      - link_watch infrastructure only sends one notification per second and
        in case of e.g. paired disconnect/connect events we get only one
        notification with last status. This makes it impossible to handle such
        situations in userspace.
      
      Redo link status changes handling in the following way:
      - Create a list of reconfig events in network device context.
      - On a reconfig event add it to the list of events and schedule
        netvsc_link_change().
      - In netvsc_link_change() ensure 2-second delay between link status
        changes.
      - Handle RNDIS_STATUS_NETWORK_CHANGE as a paired disconnect/connect event.
      Signed-off-by: NVitaly Kuznetsov <vkuznets@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      27a70af3
  3. 02 9月, 2015 1 次提交
  4. 19 8月, 2015 1 次提交
  5. 13 8月, 2015 2 次提交
  6. 16 7月, 2015 1 次提交
  7. 09 7月, 2015 1 次提交
  8. 31 5月, 2015 1 次提交
    • K
      hv_netvsc: Properly size the vrss queues · e01ec219
      KY Srinivasan 提交于
      The current algorithm for deciding on the number of VRSS channels is
      not optimal since we open up the min of number of CPUs online and the
      number of VRSS channels the host is offering. So on a 32 VCPU guest
      we could potentially open 32 VRSS subchannels. Experimentation has
      shown that it is best to limit the number of VRSS channels to the number
      of CPUs within a NUMA node.
      
      Here is the new algorithm for deciding on the number of sub-channels we
      would open up:
              1) Pick the minimum of what the host is offering and what the driver
                 in the guest is specifying as the default value.
              2) Pick the minimum of (1) and the numbers of CPUs in the NUMA
                 node the primary channel is bound to.
      Signed-off-by: NK. Y. Srinivasan <kys@microsoft.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e01ec219
  9. 18 5月, 2015 1 次提交
  10. 15 5月, 2015 1 次提交
  11. 14 5月, 2015 1 次提交
  12. 30 4月, 2015 2 次提交
  13. 15 4月, 2015 1 次提交
  14. 09 4月, 2015 2 次提交
  15. 08 4月, 2015 2 次提交
  16. 01 4月, 2015 2 次提交
  17. 30 3月, 2015 1 次提交
  18. 01 3月, 2015 1 次提交
  19. 13 11月, 2014 1 次提交
  20. 31 10月, 2014 1 次提交
  21. 23 10月, 2014 1 次提交
  22. 18 10月, 2014 1 次提交
  23. 30 9月, 2014 1 次提交
  24. 10 7月, 2014 1 次提交
  25. 20 6月, 2014 1 次提交