From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH] config: default to shared library Date: Wed, 4 Mar 2015 14:10:32 +0000 Message-ID: <20150304141032.GD544@bricha3-MOBL3> References: <1534932.rt5IAT3UZl@xps13> <54F6E6E3.50404@redhat.com> <20150304112805.GA5808@hmsreliant.think-freely.org> <20150304130848.GA544@bricha3-MOBL3> <54F7077C.1010504@redhat.com> <20150304133129.GB544@bricha3-MOBL3> <54F70B9D.7040903@redhat.com> <20150304134911.GC544@bricha3-MOBL3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev-VfR2kkLFssw@public.gmane.org" To: David Marchand Return-path: Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Wed, Mar 04, 2015 at 02:57:50PM +0100, David Marchand wrote: > On Wed, Mar 4, 2015 at 2:49 PM, Bruce Richardson > wrote: > > > On Wed, Mar 04, 2015 at 03:41:49PM +0200, Panu Matilainen wrote: > > > Right, but then there's "ivshmem" that doesn't fit that description > > either > > > AFAICS. > > > > Ah, yes, forgotten about that one! :-) > > > Well, this is out of scope, but this config file should not exist in the > first place. > From my point of view, the ivshmem implementation is just badly hooked into > the eal, and this is the only reason why ivshmem should have a build option > (disabled) by default. > > If we could cleanup this, then there would be no exception to the naming > convention. > No objections here! :-) > > -- > David Marchand