From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 6AD0FB368 for ; Thu, 31 Jul 2014 22:43:07 +0200 (CEST) Received: from uucp by smtp.tuxdriver.com with local-rmail (Exim 4.63) (envelope-from ) id 1XCxDn-0000n9-Qc; Thu, 31 Jul 2014 16:45:07 -0400 Received: from linville-x1.hq.tuxdriver.com (localhost.localdomain [127.0.0.1]) by linville-x1.hq.tuxdriver.com (8.14.8/8.14.6) with ESMTP id s6VKW1Cx008599; Thu, 31 Jul 2014 16:32:01 -0400 Received: (from linville@localhost) by linville-x1.hq.tuxdriver.com (8.14.8/8.14.8/Submit) id s6VKW1IK008598; Thu, 31 Jul 2014 16:32:01 -0400 Date: Thu, 31 Jul 2014 16:32:00 -0400 From: "John W. Linville" To: Bruce Richardson Message-ID: <20140731203200.GH17560@tuxdriver.com> References: <1406665466-29654-1-git-send-email-nhorman@tuxdriver.com> <20140730210920.GB6420@localhost.localdomain> <20140731131351.GA20718@hmsreliant.think-freely.org> <5766264.li3nkTmgY6@xps13> <20140731143228.GB20718@hmsreliant.think-freely.org> <20140731181032.GC20718@hmsreliant.think-freely.org> <20140731183631.GC6420@localhost.localdomain> <20140731195829.GG17560@tuxdriver.com> <20140731202042.GB28495@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140731202042.GB28495@localhost.localdomain> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 0/2] dpdk: Allow for dynamic enablement of some isolated features 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: Thu, 31 Jul 2014 20:43:07 -0000 On Thu, Jul 31, 2014 at 01:20:42PM -0700, Bruce Richardson wrote: > On Thu, Jul 31, 2014 at 03:58:30PM -0400, John W. Linville wrote: > > On Thu, Jul 31, 2014 at 11:36:32AM -0700, Bruce Richardson wrote: > > > > > With regards to the general approach for runtime detection of software > > > functions, I wonder if something like this can be handled by the > > > packaging system? Is it possible to ship out a set of shared libs > > > compiled up for different instruction sets, and then at rpm install > > > time, symlink the appropriate library? This would push the whole issue > > > of detection of code paths outside of code, work across all our > > > libraries and ensure each user got the best performance they could get > > > form a binary? > > > Has something like this been done before? The building of all the > > > libraries could be scripted easy enough, just do multiple builds using > > > different EXTRA_CFLAGS each time, and move and rename the .so's after > > > each run. > > > > I'm not aware of a package that does anything like that. It probably > > is possible, but I imagine that it would provoke a lot of debate > > and consternation in FESCO... > > Nothing like a bit of consternation to get the adrenaline pumping, right > :-) > BTW: what is FESCO? Fedora Engineering Steering Committee Neil and I have already felt the hot breath of FESCO on our necks regarding the Fedora DPDK package... John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.