All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: snelson@pensando.io
Cc: netdev@vger.kernel.org, parav@mellanox.com
Subject: Re: [PATCH v4 net-next 0/2] ionic: add sriov support
Date: Sun, 05 Jan 2020 14:51:16 -0800 (PST)	[thread overview]
Message-ID: <20200105.145116.517086738576726939.davem@davemloft.net> (raw)
In-Reply-To: <20200103175508.32176-1-snelson@pensando.io>

From: Shannon Nelson <snelson@pensando.io>
Date: Fri,  3 Jan 2020 09:55:06 -0800

> Set up the basic support for enabling SR-IOV devices in the
> ionic driver.  Since most of the management work happens in
> the NIC firmware, the driver becomes mostly a pass-through
> for the network stack commands that want to control and
> configure the VFs.
> 
> v4:	changed "vf too big" checks to use pci_num_vf()
> 	changed from vf[] array of pointers of individually allocated
> 	  vf structs to single allocated vfs[] array of vf structs
> 	added clean up of vfs[] on probe fail
> 	added setup for vf stats dma
> 
> v3:	added check in probe for pre-existing VFs
> 	split out the alloc and dealloc of vf structs to better deal
> 	  with pre-existing VFs (left enabled on remove)
> 	restored the checks for vf too big because of a potential
> 	  case where VFs are already enabled but driver failed to
> 	  alloc the vf structs
> 
> v2:	use pci_num_vf() and kcalloc()
> 	remove checks for vf too big
> 	add locking for the VF operations
> 	disable VFs in ionic_remove() if they are still running

Series applied, thanks Shannon.

      parent reply	other threads:[~2020-01-05 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 17:55 [PATCH v4 net-next 0/2] ionic: add sriov support Shannon Nelson
2020-01-03 17:55 ` [PATCH v4 net-next 1/2] ionic: ionic_if bits for sr-iov support Shannon Nelson
2020-01-03 17:55 ` [PATCH v4 net-next 2/2] ionic: support sr-iov operations Shannon Nelson
2020-01-05 22:51 ` David Miller [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=20200105.145116.517086738576726939.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=parav@mellanox.com \
    --cc=snelson@pensando.io \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.