netdev - [net-next 00/17][pull request] 100GbE Intel Wired LAN Driver Updates 2015-12-03

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1449188994-64940-1-git-send-email-jeffrey.t.kirsher@intel.com>
Date:	Thu,  3 Dec 2015 16:29:37 -0800
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	davem@...emloft.net
Cc:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>, netdev@...r.kernel.org,
	nhorman@...hat.com, sassmann@...hat.com, jogreene@...hat.com,
	john.ronciak@...el.com
Subject: [net-next 00/17][pull request] 100GbE Intel Wired LAN Driver Updates 2015-12-03

This series contains updates to fm10k only.

I know I am going to regret this, but Nick Krause actually submitted a good
patch for fm10k to fix error handling of fm10k_setup_tc().  There were two
calls in the function which returned an integer which was being ignored
and not handled properly.

Jacob provides the remaining fm10k patches in the series.  First change
ensures that all the logic regarding the setting of netdev features is
consolidated in one place of the driver.  Fixed an issue where an assumption
was being made on how many queues are available, especially when init_hw_vf()
errors out.  Fixed up an number of issues with init_hw() where failures
were not being handled properly or at all, so update the driver to check
returned error codes and respond appropriately.  Fixed up typecasting
issues found where either the incorrect typecast size was used or
explicitly typecast values.  Added additional debugging statistics and
rename statistic to better reflect its true value.  Added support for
ITR scaling based on PCIe link speed for fm10k.  Fixed up code comment
where "hardware" was misspelled.

The following are changes since commit 6b20da4d8f3f6a3be9f67e3207f435cfaa5f7f97:
  mlxsw: core: Change BUG to WARN in hwmon code
and are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 100GbE

Jacob Keller (16):
  fm10k: set netdev features in one location
  fm10k: reset max_queues on init_hw_vf failure
  fm10k: always check init_hw for errors
  fm10k: reinitialize queuing scheme after calling init_hw
  fm10k: Correct typecast in fm10k_update_xc_addr_pf
  fm10k: explicitly typecast vlan values to u16
  fm10k: add statistics for actual DWORD count of mbmem mailbox
  fm10k: rename mbx_tx_oversized statistic to mbx_tx_dropped
  fm10k: add TEB check to fm10k_gre_is_nvgre
  fm10k: Add support for ITR scaling based on PCIe link speed
  fm10k: introduce ITR_IS_ADAPTIVE macro
  fm10k: Update adaptive ITR algorithm
  fm10k: use macro for default Tx and Rx ITR values
  fm10k: change default Tx ITR to 25usec
  fm10k: TRIVIAL fix typo of hardware
  fm10k: TRIVIAL cleanup order at top of fm10k_xmit_frame

Nick (1):
  fm10k: Fix error handling in the function fm10k_setup_tc for certain
    function calls

 drivers/net/ethernet/intel/fm10k/fm10k.h         |  8 ++-
 drivers/net/ethernet/intel/fm10k/fm10k_ethtool.c | 14 ++---
 drivers/net/ethernet/intel/fm10k/fm10k_main.c    | 66 +++++++++++++++------
 drivers/net/ethernet/intel/fm10k/fm10k_mbx.c     |  4 ++
 drivers/net/ethernet/intel/fm10k/fm10k_mbx.h     |  4 +-
 drivers/net/ethernet/intel/fm10k/fm10k_netdev.c  | 40 ++++++++-----
 drivers/net/ethernet/intel/fm10k/fm10k_pci.c     | 75 ++++++++++++++++++------
 drivers/net/ethernet/intel/fm10k/fm10k_pf.c      | 34 ++++++++---
 drivers/net/ethernet/intel/fm10k/fm10k_type.h    | 17 +++++-
 drivers/net/ethernet/intel/fm10k/fm10k_vf.c      | 33 +++++++++--
 10 files changed, 223 insertions(+), 72 deletions(-)

-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html