From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 604103195 for ; Fri, 25 May 2018 13:22:32 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A34D7222B7; Fri, 25 May 2018 07:21:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 25 May 2018 07:21:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ZuUx83SSVeckJ/X2dAgwYJhgR9 l8xAWwHcODYjq77kk=; b=nw/mrmpLK4siqJi1ykqA/Ybpwp2e2IBrqx/Nv9kUPI pJjlq6ZwttYDjX7oG1pKXycze53bysBwWATdGg5NxC9WvDdZ4bf5UsL+CiKKAQB4 Xamq2M0I4l4a/ucKuObLcf8L34IJv79eXTj0B02aNcRK0ymnuTS8oxEtH+9XtGEj A= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ZuUx83 SSVeckJ/X2dAgwYJhgR9l8xAWwHcODYjq77kk=; b=gptlb13FrvodhswZH7305Y lSimFTZorBRfGkwpGQu/QZ1YggttDP+YhZiOcJc0yYtQj5Onp4x/BWjMkpRxgWVr GhObYqqITQfXKJJ+9YuuHy50GuC+e9fMNF14gmUeSJp8tvzaKgSkuI7JA/PMqNDF Dqxj53KohDCwjewQl4z90gE/vn04K2ytGg1YG9JOAe/NDPVqq/w8goqdFBh4akae yBVuxlLlFwBws2wLoiUFJdYWbeDY06syoI7uhA95YSQsKqURrJIBKSRgL71K11+4 0A3JNs4yiw9fq15tS40htBtMjLvw/ePFvhS2C0slpcmqRk+pWLqcmvkHkwCJv4Rw == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (22.87.136.77.rev.sfr.net [77.136.87.22]) by mail.messagingengine.com (Postfix) with ESMTPA id E54C9E42DB; Fri, 25 May 2018 07:21:21 -0400 (EDT) From: Thomas Monjalon To: Kevin Wilson Cc: dev@dpdk.org Date: Fri, 25 May 2018 13:21:18 +0200 Message-ID: <2384240.a6VFuv6gqB@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Kernel Module dependency in DPDK 18.05-rc5 and earlier DPDK releases 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: Fri, 25 May 2018 11:22:32 -0000 25/05/2018 11:55, Kevin Wilson: > Hi, > > I am facing the following issue in DPDK 18.05-rc5 (I saw it also with earlier > releases of DPDK from the last year). The issue is with defining > dependency on a kernel module in a PMD. > I want to develop a PMD which requiers that before running DPDK app which > uses this PMD, a specified kernel module is required to be insmoded. > I tried to add a call to RTE_PMD_REGISTER_KMOD_DEP in my PMD, > specifying a required > kernel module, and I expected that when calling a DPDK app which uses > this PMD it will shout that such a kernel module is not loaded, but this did not > happen. No such check is implemented currently. You can try to implement a check in EAL in the probing function.