netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
	jogreene@redhat.com, john.ronciak@intel.com
Subject: Re: [net-next 0/5][pull request] Intel Wired LAN Driver Updates 2015-09-28
Date: Mon, 28 Sep 2015 17:33:54 -0700	[thread overview]
Message-ID: <1443486834.2864.1.camel@intel.com> (raw)
In-Reply-To: <1443468800-37102-1-git-send-email-jeffrey.t.kirsher@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1664 bytes --]

On Mon, 2015-09-28 at 12:33 -0700, Jeff Kirsher wrote:
> This series contains updates to i40e, i40evf and igb to resolve
> issues
> seen and reported by Red Hat.
> 
> Kiran moves i40e_get_head() in preparation for the refactor of the Tx
> timeout logic, so that it can be used in other areas of the driver.
> Refactored the driver timeout logic by issuing a writeback request
> via
> a software interrupt to the hardware the first time the driver
> detects
> a hang.  This was due to the driver being too aggressive in resetting
> a
> hung queue.
> 
> Shannon adds the GRE protocol to the transmit checksum encoding.
> 
> Anjali fixes an issue of forcing writeback too often, which caused us
> to
> not benefit from NAPI.  We now disable force writeback in the clean
> routine for X710 and XL710 adapters.  The X722 adapters do not enable
> interrupt to force a writeback and benefit from WB_ON_ITR and so
> force
> WB is left enabled for those adapters.
> 
> Stefan Assmann provides a fix for igb where SR-IOV was not getting
> enabled properly and we ran into a NULL pointer if the max_vfs module
> parameter is specified.  This is prevented by setting the
> IGB_FLAG_HAS_MSIX bit before calling igb_probe_vfs().
> 
> The following are changes since commit
> 34c2d9fb0498c066afbe610b15e18995fd8be792:
>   bridge: Allow forward delay to be cfgd when STP enabled
> and are available in the git repository at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue
> master

I need to add one more patch to this series from Anjali which resolves
a possible deadlock issue.  So v2 of the series is coming shortly.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2015-09-29  0:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 19:33 [net-next 0/5][pull request] Intel Wired LAN Driver Updates 2015-09-28 Jeff Kirsher
2015-09-28 19:33 ` [net-next 1/5] i40e: Move i40e_get_head into header file Jeff Kirsher
2015-09-28 19:33 ` [net-next 2/5] i40e/i40evf: refactor tx timeout logic Jeff Kirsher
2015-09-28 19:33 ` [net-next 3/5] i40e: add GRE tunnel type to csum encoding Jeff Kirsher
2015-09-28 19:33 ` [net-next 4/5] i40e: Fix RS bit update in Tx path and disable force WB workaround Jeff Kirsher
2015-09-28 19:33 ` [net-next 5/5] igb: assume MSI-X interrupts during initialization Jeff Kirsher
2015-09-29  0:33 ` Jeff Kirsher [this message]

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=1443486834.2864.1.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=jogreene@redhat.com \
    --cc=john.ronciak@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).