From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linville@tuxdriver.com>
Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58])
 by dpdk.org (Postfix) with ESMTP id BB83FB368
 for <dev@dpdk.org>; Thu, 31 Jul 2014 21:58:12 +0200 (CEST)
Received: from uucp by smtp.tuxdriver.com with local-rmail (Exim 4.63)
 (envelope-from <linville@tuxdriver.com>)
 id 1XCwWK-0000R0-KB; Thu, 31 Jul 2014 16:00:12 -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 s6VJwUQg007304; 
 Thu, 31 Jul 2014 15:58:30 -0400
Received: (from linville@localhost)
 by linville-x1.hq.tuxdriver.com (8.14.8/8.14.8/Submit) id s6VJwUpW007303;
 Thu, 31 Jul 2014 15:58:30 -0400
Date: Thu, 31 Jul 2014 15:58:30 -0400
From: "John W. Linville" <linville@tuxdriver.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Message-ID: <20140731195829.GG17560@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140731183631.GC6420@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 <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: Thu, 31 Jul 2014 19:58:13 -0000

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...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.