From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [net-next 00/14][pull request] 40GbE Intel Wired LAN Driver Updates 2018-09-18 Date: Tue, 18 Sep 2018 19:42:53 -0700 (PDT) Message-ID: <20180918.194253.1313750124665601146.davem@redhat.com> References: <20180918223731.31876-1-jeffrey.t.kirsher@intel.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com, jogreene@redhat.com To: jeffrey.t.kirsher@intel.com Return-path: Received: from mx1.redhat.com ([209.132.183.28]:39134 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725817AbeISISg (ORCPT ); Wed, 19 Sep 2018 04:18:36 -0400 In-Reply-To: <20180918223731.31876-1-jeffrey.t.kirsher@intel.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Jeff Kirsher Date: Tue, 18 Sep 2018 15:37:17 -0700 > This series contains changes to i40evf so that it becomes a more > generic virtual function driver for current and future silicon. > > While doing the rename of i40evf to a more generic name of iavf, > we also put the driver on a severe diet due to how much of the > code was unneeded or was unused. The outcome is a lean and mean > virtual function driver that continues to work on existing 40GbE > (i40e) virtual devices and prepped for future supported devices, > like the 100GbE (ice) virtual devices. > > This solves 2 issues we saw coming or were already present, the > first was constant code duplication happening with i40e/i40evf, > when much of the duplicate code in the i40evf was not used or was > not needed. The second was to remove the future confusion of why > future VF devices that were not considered "40GbE" only devices > were supported by i40evf. > > The thought is that iavf will be the virtual function driver for > all future devices, so it should have a "generic" name to properly > represent that it is the VF driver for multiple generations of > devices. > > The last patch in this series is unreleated to the iavf conversion > and just has to do with a MODULE_LICENSE correction. > > Known Caveats: > Existing user space configurations may have to change, but the module > alias in patch 1 helps a bit here. Ok, let's see how this goes. Pulled, thanks.