From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by dpdk.org (Postfix) with ESMTP id A7031AF89 for ; Mon, 14 Apr 2014 17:33:06 +0200 (CEST) Received: by mail-pd0-f177.google.com with SMTP id y10so8188157pdj.36 for ; Mon, 14 Apr 2014 08:33:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=rPburVF0aWFiF1Kk8/wq4CgJONuxbuUuHmLMsr5N0R0=; b=kf1NHJj20JyptXE6KjT+go3X1cQTBeP2dI7uWARuRNHzCze9uzPhP4T8vv5QuoliOc 41Xz2Abqn/msgYbMudBNKxxmVvpJMWh3FyGnwne/OVqzj/kyWZAAt70L5T3euhBVEBcB T/D0+goh8KBnYzZjNVThpk4pPE7ve2jN0uV64ux4xo5ciChhKKvbBnVX8ozV0GrLKNTQ bejnhtJg6eo+JGzfnE7uSlJhKaGCOtK5Xbl3kmSiEuVDW43gBnzelP7p8sFcjd3jYKe/ 2otbgm3lXQlPAQUsB0Cfh460I2fzDH2DhRFCpCItKHBRKLF26K3g7FLoquPbI+RbxUu9 DJcg== X-Gm-Message-State: ALoCoQm1ugYMc2PNxbkxUdjcrLD+m9NRvEVgUw0GzBFve0Zm/7rv1a2OcrczCSbveUf/xFI+1caj X-Received: by 10.66.65.169 with SMTP id y9mr3590958pas.145.1397489586415; Mon, 14 Apr 2014 08:33:06 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51]) by mx.google.com with ESMTPSA id xg8sm39469255pac.26.2014.04.14.08.33.05 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 14 Apr 2014 08:33:06 -0700 (PDT) Date: Mon, 14 Apr 2014 08:33:03 -0700 From: Stephen Hemminger To: "Burakov, Anatoly" Message-ID: <20140414083303.09cb43ed@nehalam.linuxnetplumber.net> In-Reply-To: References: <20140411092435.29e06974@nehalam.linuxnetplumber.net> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] IGB_UIO port unbinding 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: Mon, 14 Apr 2014 15:33:07 -0000 On Mon, 14 Apr 2014 08:57:54 +0000 "Burakov, Anatoly" wrote: > Hi Stephen, > > > I actually liked the unbind code that was there. It meant that additional logic > > did not have to be added to the startup script to do PCI discovery and > > finding/mapping devices. > > > > As it is the EAL startup process is a bit of a mess. It assumes that various bits > > of information and infrastructure are already in place prior to starting the > > DPDK application. > > I would argue that it's not the responsibility of the application to set up its environment. The EAL startup process is indeed a bit all over the place, but the alternative would be worse. Those "various bits of information and infrastructure" you're referring to include, say, hugepages - I don't think it's a good idea for an application to meddle with system's hugepages any more than I think it's a good idea for it to meddle with the driver bindings. > > Plus, current state of affairs makes for headaches in the future when support for other drivers is implemented (say, VFIO). It's much better to move the responsibility of binding the drivers to the user, and DPDK provides quite convenient means to do that (the PCI binding Python script) and also a centralized script to prepare the DPDK environment without much hassle (the setup.sh). > > Best regards, > Anatoly Burakov > DPDK SW Engineer > The problem is that doing the initialization requires duplicating all the logic to probe the PCI bus and do blacklisting etc in the startup application.