From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com
Subject: [net 0/2][pull request] Intel Wired LAN Driver Updates 2019-09-11
Date: Wed, 11 Sep 2019 09:49:53 -0700 [thread overview]
Message-ID: <20190911164955.10644-1-jeffrey.t.kirsher@intel.com> (raw)
This series contains fixes to ixgbe.
Alex fixes up the adaptive ITR scheme for ixgbe which could result in a
value that was either 0 or something less than 10 which was causing
issues with hardware features, like RSC, that do not function well with
ITR values that low.
Ilya Maximets fixes the ixgbe driver to limit the number of transmit
descriptors to clean by the number of transmit descriptors used in the
transmit ring, so that the driver does not try to "double" clean the
same descriptors.
The following are changes since commit f4b752a6b2708bfdf7fbe8a241082c8104f4ce05:
mlx4: fix spelling mistake "veify" -> "verify"
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-queue 10GbE
Alexander Duyck (1):
ixgbe: Prevent u8 wrapping of ITR value to something less than 10us
Ilya Maximets (1):
ixgbe: fix double clean of Tx descriptors with xdp
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 4 ++-
drivers/net/ethernet/intel/ixgbe/ixgbe_xsk.c | 29 +++++++------------
2 files changed, 14 insertions(+), 19 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-11 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 16:49 Jeff Kirsher [this message]
2019-09-11 16:49 ` [net 1/2] ixgbe: Prevent u8 wrapping of ITR value to something less than 10us Jeff Kirsher
2019-09-11 16:49 ` [net 2/2] ixgbe: fix double clean of Tx descriptors with xdp Jeff Kirsher
2019-09-11 23:08 ` [net 0/2][pull request] Intel Wired LAN Driver Updates 2019-09-11 David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190911164955.10644-1-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox