From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v3 0/5] improve tap behavior Date: Fri, 12 May 2017 15:04:56 +0100 Message-ID: <10f1b628-b21f-7e07-de8b-00dfe2393291@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: Pascal Mazon , dev@dpdk.org Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id E53941C4A for ; Fri, 12 May 2017 16:04:59 +0200 (CEST) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 5/12/2017 2:01 PM, Pascal Mazon wrote: > The tap does not behave properly in some cases. > > It is generally expected that a real device should be available once the > probing has been done. > > It is also better to check if an operation (here, setting MAC) is > mandatory before performing it. Typically in cases where the remote > netdevice is a VF with limited capabilities. > > This series ensures that the tap works more logically. > > v3 changes: > - rebase on top of next-net/master > > v2 changes: > - fix uninitialized fd variable > > Pascal Mazon (5): > net/tap: add debug messages > net/tap: remove unnecessary functions > net/tap: drop unnecessary nested block > net/tap: create netdevice during probing > net/tap: do not set remote MAC if not necessary Series applied to dpdk-next-net/master, thanks.