From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id CA2D6AAB5 for ; Mon, 16 Apr 2018 19:50:13 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 400972108D; Mon, 16 Apr 2018 13:50:13 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 16 Apr 2018 13:50:13 -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=PsClBiXQLCkSjj7k0N+Qgjkg0S 1vZxLHNNKXps3jx/0=; b=rbYoFejlIMnrJHJJYDC3goK8SWy1HCUFsDiltHRCfp feaB5HCx1B97pY2r2HvvhLWJClFxLcZ8kcPSppTJbsLyx4CZ9/zCP/8HpgcuX1hr pEGC775soWe8JoDkgUXoVkcQBGVsi+8OVppll48LeZ7t7aVNZpKzc+PJsFSSmy+Q 4= 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=PsClBi XQLCkSjj7k0N+Qgjkg0S1vZxLHNNKXps3jx/0=; b=L9i+j+bk9B8sggpVEM/zO4 qTp9MFqtuGkSaxiQkWMqZ0Pkb3xFGyX1vsU5AXnAf+VEIG8rOpz4AUSuMrOigMNq OJNXT2ZdavwctSkcx4gvZjHF5HRxq0SN+57/LP1MMrD3fQoxiz0XuGFA6fJLhNmG pTNSqNZC+lcUQDai58bWM6H2tk//ClTXUt2XhDo6UG7g0gyUtGnUtCru3RrAX7n4 hac6nUMBsb3D1mcpHZCKN8K2ssCKiq1lmpm2WGZU3RyxTE2K8tK/DuNR8DRw+U06 2Mfrq1IDd9wm0e80AEsswST1U0MR/R0xDFybw32p7J0nTGo2yXsA2T7h7ODsKWKQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id EA5EDE4ED0; Mon, 16 Apr 2018 13:50:11 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger , Bruce Richardson Cc: Matan Azrad , "Burakov, Anatoly" , "dev@dpdk.org" , "pmatilai@redhat.com" , "david.marchand@6wind.com" , "jia.guo@intel.com" , "konstantin.ananyev@intel.com" , "fbl@redhat.com" Date: Mon, 16 Apr 2018 19:50:10 +0200 Message-ID: <12594971.AWg2Dei6cb@xps> In-Reply-To: <20180416095723.0d7698c7@xeon-e3> References: <2407757.yEAnF6RcS7@xps> <20180416095723.0d7698c7@xeon-e3> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] kernel binding of devices + hotplug 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: Mon, 16 Apr 2018 17:50:14 -0000 16/04/2018 18:57, Stephen Hemminger: > Buried under this discussion is the fact that the Mellanox bifurcated driver > behaves completely differently from every other driver. This makes coming to > a common solution much harder. The bifurcated model has advantages and disadvantages, > in this case it is a disadvantage since it is not easy to manage usage when > it is a shared resource. The bifurcated model can apply to more cases than Mellanox. For instance, the AF_XDP PMD will be bifurcated. In the case of AF_XDP, you don't need to bind a kernel module to the device. We have a good idea of how to program the right binding inside DPDK: depending on how the device is configured by the application or from the command line options, we can guess which binding is expected. We need to compare it with how we could integrate the same "transparent binding" with udev/driverctl. The system tools are nice for persistent and global configuration. The other requirement is to be able to run a one-shot DPDK application without changing the persistent system configuration. We may need to hook udev/driverctl live to make it happen.