From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com
 [209.85.220.49]) by dpdk.org (Postfix) with ESMTP id 11EE05941
 for <dev@dpdk.org>; Tue,  2 Sep 2014 20:10:59 +0200 (CEST)
Received: by mail-pa0-f49.google.com with SMTP id kq14so15068660pab.8
 for <dev@dpdk.org>; Tue, 02 Sep 2014 11:15:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=jox9AlRBoOf2xda7nof9oDLNDTta2AvmvIoK5G/Kn+c=;
 b=DVLHyElW9RtKhHxTE814X5Yyy9+RiePRjoWRN5tqw1LRIZfpdlYX6m4qfP2LGSNLYf
 GzrD62X8xf4G8HUYXu03rSL3PsS9tqroV6i+G/UsD7GpctRywk2S+IRxO97HnWKFFMK7
 eik3sSGC8rT1OlgzcHjSDe8K/BSWLME6sIDL0C2fMSSgO3gFSC+5YxAfNzKISZqPEeb6
 V2iKapGcpHnIAxPYoCNhYAzkVnWgFjiAfTmQhiDKROzWoiJ4FZaGH3Hj+OH2Mh5GXZk7
 Mve/js5vC2dSYPResg0+DFTiDPctYfDpI0KELnc0ovV3YqINfgS2waWXh0hjvvxCyoYs
 eRsQ==
X-Gm-Message-State: ALoCoQlQeS5o/AkRPpkzNI4vvQzcfrNq0GKBGo34jITwKOWDcg7XNzR3u1Cy01bcQ6PtNVs6sQ0E
X-Received: by 10.66.183.235 with SMTP id ep11mr22100584pac.113.1409681732092; 
 Tue, 02 Sep 2014 11:15:32 -0700 (PDT)
Received: from urahara (static-50-53-65-80.bvtn.or.frontiernet.net.
 [50.53.65.80])
 by mx.google.com with ESMTPSA id ja3sm4610407pbd.73.2014.09.02.11.15.31
 for <multiple recipients>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 02 Sep 2014 11:15:31 -0700 (PDT)
Date: Tue, 2 Sep 2014 11:15:28 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Declan Doherty <declan.doherty@intel.com>
Message-ID: <20140902111528.74aa7928@urahara>
In-Reply-To: <1409560289-29558-1-git-send-email-declan.doherty@intel.com>
References: <1408456313-28812-1-git-send-email-declan.doherty@intel.com>
 <1409560289-29558-1-git-send-email-declan.doherty@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/6] link bonding
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2014 18:11:00 -0000

On Mon,  1 Sep 2014 09:31:23 +0100
Declan Doherty <declan.doherty@intel.com> wrote:

> This patch set adds support for link status interrupt in the link bonding
> pmd. It also contains some patches to tidy up the code structure and to
> of the link bonding code and to fix bugs relating to transmission 
> failures in the under lying slave pmd which could lead to leaked mbufs. 

Does this work when interfaces being bonded do not support link state
like VF's and some other virtual devices (like vmxnet3?).

I am concerned that the flag to say whether device support LSC or not
is in drv_flags which is normally invariant. So either bond has to simulate
link state if slave devices do not support (by polling) or provide another
mechanism for application to determine availablity of link state.