From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 31D2312A8 for ; Tue, 31 Jan 2017 15:21:03 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga105.jf.intel.com with ESMTP; 31 Jan 2017 06:21:02 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,315,1477983600"; d="scan'208";a="928560453" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.38]) ([10.237.220.38]) by orsmga003.jf.intel.com with ESMTP; 31 Jan 2017 06:21:00 -0800 To: Thomas Monjalon , Pablo de Lara , Fan Zhang References: <20170131115950.25660-1-ferruh.yigit@intel.com> <20170131115950.25660-2-ferruh.yigit@intel.com> <1747389.KZLHpWvR9T@xps13> Cc: dev@dpdk.org From: Ferruh Yigit Message-ID: <46e1fa65-9013-121f-da7f-51eaa24cf6df@intel.com> Date: Tue, 31 Jan 2017 14:20:59 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <1747389.KZLHpWvR9T@xps13> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH 2/2] mk: move crypto scheduler library X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 14:21:03 -0000 On 1/31/2017 2:10 PM, Thomas Monjalon wrote: > 2017-01-31 11:59, Ferruh Yigit: >> There is already a block for crypto libraries, move the PMD library to >> that block. >> >> This prevents extra ifdef check for cryptodev. > > That's why I thought also when reading this patch: > http://dpdk.org/commit/dbb336407 > Then I've read its message: > "Different than other cryptodev PMDs, scheduler PMD is required to be built > as shared libraries." This patch requires following patch for shared library compilation: http://dpdk.org/dev/patchwork/patch/20091/ I tried to separate patches, but it seems not able to completely. Overall, for this patch and above referenced one, need to decide how to link PMDs with APIs (like bonding, xenvirt) > > I guess the explanation is that it has an API (like bonding has): > drivers/crypto/scheduler/rte_cryptodev_scheduler.h > > However, it is neither referenced in doc/api/doxy-api.conf nor > doc/api/doxy-api-index.md. > > <...>