From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com
 [209.85.220.41]) by dpdk.org (Postfix) with ESMTP id F2028B126
 for <dev@dpdk.org>; Fri, 13 Jun 2014 23:59:05 +0200 (CEST)
Received: by mail-pa0-f41.google.com with SMTP id fb1so102740pad.0
 for <dev@dpdk.org>; Fri, 13 Jun 2014 14:59:21 -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=nTgsjeNojTMQCqsZF6S8XzMfYUPYLmCXY+kdaHkICL8=;
 b=Hbmb2lRRbWmF0an+PtMk8SD/lvCCCcKXUwvnaKoEi5qLkKmre1/p6FHGFr8ge+vYMp
 78s3fRFN0zEWb88UJwtX6dWgjFhMZ32Y3RPZJ+KQWzzTSJ6kY3ELxdZ/e+DsCd46OFsh
 Tnb6ZXHz7ca0R5lcIZLs0jECBtzAL3MyJwbN72klW+dW9/DjROOT0ay0RHrPYTodx9RX
 UzN1/YcvdsbHfj8/x9qo0hRdwwuqs3yF82mms/Ts1pKQFTa/5MvWj+0dOZzYdPtMJ/1I
 SqqhtQGq5kCbFXVvQOrTsQgpxRqBioAgvYeeWiI2bJdGv9BQHA4+kaQU7j3lHXWaFydE
 d+4g==
X-Gm-Message-State: ALoCoQlxS5xQWrRynz9Rqe2xczhENhXj1uLTDtJ8VhJluwr95vCOddSVsaBi+Bs8euist6zgCMWR
X-Received: by 10.68.189.68 with SMTP id gg4mr6596880pbc.42.1402696761085;
 Fri, 13 Jun 2014 14:59:21 -0700 (PDT)
Received: from nehalam.linuxnetplumber.net
 (static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51])
 by mx.google.com with ESMTPSA id se3sm5357519pbb.80.2014.06.13.14.59.20
 for <multiple recipients>
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Fri, 13 Jun 2014 14:59:20 -0700 (PDT)
Date: Fri, 13 Jun 2014 14:59:18 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Declan Doherty <declan.doherty@intel.com>
Message-ID: <20140613145918.5faebfde@nehalam.linuxnetplumber.net>
In-Reply-To: <258914f35917ae07dddc991ac9726542964dce44.1402662300.git.declan.doherty@intel.com>
References: <cover.1401287412.git.declan.doherty@intel.com>
 <258914f35917ae07dddc991ac9726542964dce44.1402662300.git.declan.doherty@intel.com>
X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 2/5] Link Bonding PMD Library
 (librte_eal/librte_ether link bonding support changes)
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: Fri, 13 Jun 2014 21:59:06 -0000

On Fri, 13 Jun 2014 15:41:59 +0100
Declan Doherty <declan.doherty@intel.com> wrote:

> Updating functionality in EAL to support adding link bonding
> devices via =C3=A2=E2=82=AC=E2=80=9Cvdev option. Link bonding devices wil=
l be
> initialized after all physical devices have been probed and
> initialized.
>=20
> Signed-off-by: Declan Doherty <declan.doherty@intel.com>

The DPDK is used by both static (demo style) applications and dynamic
applications that need to be able to modify parameters while running.
The tendency of the code has been to have values that can only be set
at initialization, and this kind of inflexibility is hard to fix.

The whole dev args style of configuration is a poor design for those
reasons.  How do you support creating additional bond devices at runtime?

Remember what works for a demo doesn't make a good API for real world.