From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by dpdk.org (Postfix) with ESMTP id 36AE847D2 for ; Wed, 29 Jan 2014 19:41:04 +0100 (CET) Received: by mail-pa0-f51.google.com with SMTP id ld10so2107393pab.24 for ; Wed, 29 Jan 2014 10:42:22 -0800 (PST) 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=b1jiYQR/PRkE4eQ3DhGFT54Pu68gm1gLqNHlUcl8nI8=; b=gtFpqDHVhecBfvnX4JoWfDkI2Xk8xLlD1jCNwiBagQZBg+1klrBQJgq6wmRlPahdRx z+e9HqVLXqx/CgS3cUaF6v7j1mkEm6BofN8qti3+NbXnm084ftxUeKT0lLwugdYY6jmw krVDxDLGSo3V9t2JxD06PwzevW5rSjRD6gDhXvbJ+3ZylfuBN3OVoZ2NUKjG60PIa0/Y RwGFh35us9z6AaSns6ORkCxjhdSH5fcap+slO2tKRbLPAAZOuycyKtO50VhV8cuGv1fD VcvGLXefk3d4k3C/3qpwGWpwVln2WNZfWebgVkvSQjibZlbCfA7ZBTFOmN4R7ueA9Zfy Xsug== X-Gm-Message-State: ALoCoQm6iGGCh8ycQSDHrjrkCaQCAMpQ/FfIUvTSDYkFbnj6CPSPrL9o8o2WmnCQjWAgm00RE502 X-Received: by 10.66.181.70 with SMTP id du6mr9785994pac.122.1391020942523; Wed, 29 Jan 2014 10:42:22 -0800 (PST) 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 iq10sm9519302pbc.14.2014.01.29.10.42.21 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 29 Jan 2014 10:42:22 -0800 (PST) Date: Wed, 29 Jan 2014 10:42:18 -0800 From: Stephen Hemminger To: Thomas Graf Message-ID: <20140129104218.48c9a1a0@nehalam.linuxnetplumber.net> In-Reply-To: <52E936D9.4010207@redhat.com> References: <1390873715-26714-1-git-send-email-pshelar@nicira.com> <52E7D13B.9020404@redhat.com> <52E8B88A.1070104@redhat.com> <52E8D772.9070302@6wind.com> <52E8E2AB.1080600@redhat.com> <52E92DA6.9070704@6wind.com> <52E936D9.4010207@redhat.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@openvswitch.org" , dev@dpdk.org, Gerald Rogers , dpdk-ovs@ml01.01.org Subject: Re: [dpdk-dev] [ovs-dev] [PATCH RFC] dpif-netdev: Add support Intel DPDK based ports. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 18:41:04 -0000 On Wed, 29 Jan 2014 18:14:01 +0100 Thomas Graf wrote: > On 01/29/2014 05:34 PM, Vincent JARDIN wrote: > > Thomas, > > > > First and easy answer: it is open source, so anyone can recompile. So, > > what's the issue? > > I'm talking from a pure distribution perspective here: Requiring to > recompile all DPDK based applications to distribute a bugfix or to > add support for a new PMD is not ideal. > > So ideally OVS would have the possibility to link against the shared > library long term. > > > I get lost: do you mean ABI + API toward the PMDs or towards the > > applications using the librte ? > > Towards the PMDs is more straight forward at first so it seems logical > to focus on that first. > > A stable API and ABI for librte seems required as well long term as > DPDK does offer shared libraries but I realize that this is a stretch > goal in the initial phase. I would hate to see the API/ABI nailed down. We have lots of bug fixes and new drivers that are ready to contribute, but most of them have some change to existing ABI.