From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <stephen@networkplumber.org> Received: from mail-pf0-f172.google.com (mail-pf0-f172.google.com [209.85.192.172]) by dpdk.org (Postfix) with ESMTP id 26BB71B679 for <dev@dpdk.org>; Sun, 15 Apr 2018 03:48:49 +0200 (CEST) Received: by mail-pf0-f172.google.com with SMTP id o16so8937142pfk.9 for <dev@dpdk.org>; Sat, 14 Apr 2018 18:48:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t0YwZ18vbyqTIJ07omgDWqo6MF2W/7e6+UUpn/4XAkA=; b=a606ngEmoya+2AmiXG2gFVEX46adxD7XlI2B6N5c/rN4VVVQVnhmOMUnM0exZr9kh7 DNqfv2tiN86qYw01HVQMu4gyHIJV3ABU5zvn+hUp4UryI8vcvP7aTYqY/9UHdoh4TzrA bTGLupGBi6uO1ERckAz6xx/jpzmeLvOZ+6e8j6un9+jqU1g8wgzdgPD8dB6eJFwXunKP x7UEO/Hs9bgxAvTp//otTEl4ULTfpi+6IsrlCjxDcA29XAaFmkYThH1DbHeoPQtdcygf jmLQz9zLFuwGjl4hp7txUMyZHw9ea7ZEEZ0TC0cVmM6ClWJhZiwvMB5XKxMlLyeTN39V YOOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t0YwZ18vbyqTIJ07omgDWqo6MF2W/7e6+UUpn/4XAkA=; b=fWDOqitFiNFNP1O2Dsg+A6cB5F3KnvtvgCOrhyXzFX6IO2pkQCLTnH1jGD0KLECAGp FDRWxQfnpm4w9SGTQ2+CCyYKbEQEc2DaCNzpkyYLBnxsAK28lP/Tt4uYZE9l4S2pf7X0 GKglxpfe65t8Ed4+X7f0wRwJxHDR7FPdID62fjElznmp8Exwm00/ixmHefZMt53lBJGV yY+6iC0ZkA7zVM8pCjMfHF5Qmtk49zLM8g+a2b7RKUueWCuSa3kEAMWgevyuSSTXNOHf KoVQcgt64VACgAq/OtFQxFlGXzVroViNhJ8GPJMZA51bV6FxiXMgVkZLo1VR3PeObmTa uQBg== X-Gm-Message-State: ALQs6tCazzJPF6jMiUjNGDS+BtnyuaogO3kQS8Xp+FkDCP5RN4msyrQM QsFRiimt2EGj47H3UiS5qbD34Kb3YFV9j1q/FkUtJQ== X-Google-Smtp-Source: AIpwx48q9EB1+C8MqBNI0kNCJD5dzv48Z2UE5Aethq5VDZ5CNPlzvZjU7D3PNTJ5r02W6c9HmphmykeU8jf0YVjm/q0= X-Received: by 10.99.190.75 with SMTP id g11mr8558040pgo.127.1523756928037; Sat, 14 Apr 2018 18:48:48 -0700 (PDT) MIME-Version: 1.0 References: <2407757.yEAnF6RcS7@xps> In-Reply-To: <2407757.yEAnF6RcS7@xps> From: Stephen Hemminger <stephen@networkplumber.org> Date: Sun, 15 Apr 2018 01:48:36 +0000 Message-ID: <CAOaVG14YHng1N5XXkm1nBYKiR-rVzFrWgtsDK2Hc2yjT9ygGDw@mail.gmail.com> To: Thomas Monjalon <thomas@monjalon.net> Cc: dev@dpdk.org, bruce.richardson@intel.com, anatoly.burakov@intel.com, pmatilai@redhat.com, david.marchand@6wind.com, jia.guo@intel.com, matan@mellanox.com, konstantin.ananyev@intel.com, fbl@redhat.com Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 <dev.dpdk.org> List-Unsubscribe: <https://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: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Sun, 15 Apr 2018 01:48:49 -0000 My vote is to work with udev and not try to replace it. Driverctl works well. Just not for bifurcated driver On Fri, Apr 13, 2018, 9:31 AM Thomas Monjalon <thomas@monjalon.net> wrote: > It's time to think (again) how we bind devices with kernel modules. > We need to decide how we want to manage hotplugged devices with DPDK. > > A bit of history first. > There was some code in DPDK for bind/unbind, but it has been removed > in DPDK 1.7 - http://dpdk.org/commit/5d8751b83 > Copy of the commit message (in 2014): > " > The bind/unbind operations should not be handled by the eal. > These operations should be either done outside of dpdk or > inside the PMDs themselves as these are their problems. > " > > The question raised at this time (4 years ago) is still under discussion. > Should we manage binding inside or outside DPDK? > Should it be controlled in the application or in the OS base? > > As you know, we use dpdk-devbind.py. > This tool lacks two major features: > - persistent configuration > - hotplug > > If we consider that the DPDK applications should be able to apply its own > policy to choose the devices to bind, then we need to implement binding > in the PMD (with EAL helpers). > > On the other hand, if we consider that it is the system responsibility, > then we could choose systemd/udev and driverctl. > > The debate is launched! > > Please find more details in the references below. > > Announce of driverctl: > http://dpdk.org/ml/archives/dev/2015-December/029500.html > Repository of driverctl: > https://gitlab.com/driverctl/driverctl > > Discussion about binding script and driverctl: > http://dpdk.org/ml/archives/dev/2018-April/095687.html > > Patch to implement binding in DPDK (for hotplug): > http://dpdk.org/ml/archives/dev/2018-April/095714.html > > Discussion in the same hotplug series: > http://dpdk.org/ml/archives/dev/2018-April/097058.html > > > >