From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4C31D457D1; Tue, 20 Aug 2024 11:49:47 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 02B2F4026C; Tue, 20 Aug 2024 11:49:47 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 2F549400D6 for ; Tue, 20 Aug 2024 11:49:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1724147384; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SBvvq+h6SArokwRb+ImulkRTZ3RV7GP4BRLcJ18YBjw=; b=JujoDgDcEAjdgVjwi7gCOoSCrjvWiE5pp+rHkkopDbrq/IfpHV04WgLyqxNjfz7DTXIm9c p5AjVNYEHsdWdRWokLHl77QaJNzS6mvqmouHklb21l5k9IRp++0DQsLgxlp6kUEgDpbfXx JNth+DIhLu2f2ZHSWFxUFrM4B9SLiOo= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-433-Nhu9jV8vM3OrYZ8omgqh1Q-1; Tue, 20 Aug 2024 05:49:43 -0400 X-MC-Unique: Nhu9jV8vM3OrYZ8omgqh1Q-1 Received: by mail-wm1-f72.google.com with SMTP id 5b1f17b1804b1-42808685ef0so46245735e9.2 for ; Tue, 20 Aug 2024 02:49:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724147382; x=1724752182; h=in-reply-to:references:user-agent:to:from:cc:subject:message-id :date:content-transfer-encoding:mime-version:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=SBvvq+h6SArokwRb+ImulkRTZ3RV7GP4BRLcJ18YBjw=; b=h1ObaZaAhF+8+zxwFKtw2COwog8kJM5rAkquU3rNuoBH1xaPaRd7Fct2YpDJcR9PTJ gse6OcRU+TKvwKBRwZNXqHDdBmcOld6foSbgHRWFuigCbK8KI0X2o54Qhru6TFAhc19Z /1MA7SCLqK7PstXUAVmwx4OKR/366YVdf1O8PA+bGXDINGInsg3SG9uZ59HUjgI8d3vt 0EcwB4lr152LY0EnesZQazvuCfKP9r7UyFFLCjDq4CDRrY8zyCCgc+794kpa8KNLCpGS 2q0xE4K+3HmycqPrbT22gjzxnFOYNUlJ+Ix83kEjvw2dap4nDkIjWD6kwYJit/QYDjpK zspQ== X-Forwarded-Encrypted: i=1; AJvYcCVZ5CxOHPdsIwzbaysI778dhu3lOHSA9731WSzCr35T6kuHdsxGmeaLK7hQz9bVS/mENyrSPBzHmgDHhek= X-Gm-Message-State: AOJu0Yxhr0qmxliVGFnGwfGDlVOFmnO7GikL0/X+iel3iGJ4dTL4td/m gABrA5zJlDdT4ZFEJvzhonfbU6tNc+/q+cvfcGtG81+/2741F+rg+E9p8G+kLXnvQ8noI1Wnfm4 d0LV46BqrhRIMn/k6I9ktTQ39WP/HK3EYn9LOGIvI X-Received: by 2002:a05:600c:4f8d:b0:427:d713:a5d3 with SMTP id 5b1f17b1804b1-429ed79daa4mr89827925e9.11.1724147382025; Tue, 20 Aug 2024 02:49:42 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFC7c0v3cCanel9Jq72o5SOFUxpeLYLSgAyECBOaTE6F8ZL0mGB6cmWYpoAici/XqEHJ38EDQ== X-Received: by 2002:a05:600c:4f8d:b0:427:d713:a5d3 with SMTP id 5b1f17b1804b1-429ed79daa4mr89827745e9.11.1724147381498; Tue, 20 Aug 2024 02:49:41 -0700 (PDT) Received: from localhost (2a01cb00025433006239e1f47a0b2371.ipv6.abo.wanadoo.fr. [2a01:cb00:254:3300:6239:e1f4:7a0b:2371]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-3718985a347sm12752383f8f.60.2024.08.20.02.49.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Aug 2024 02:49:41 -0700 (PDT) Mime-Version: 1.0 Date: Tue, 20 Aug 2024 11:49:40 +0200 Message-Id: Subject: Re: [PATCH v2 4/4] usertools/dpdk-devbind: print NUMA node Cc: From: "Robin Jarry" To: "Burakov, Anatoly" , User-Agent: aerc/0.18.2-29-g7dd0fdeda6c9 References: <7dd3a055-d2ce-4dd9-b9df-ae95e69d4417@intel.com> In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8; format=Flowed X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Burakov, Anatoly, Aug 20, 2024 at 11:40: > I have heard about driverctl for a long time in context of devbind, and= =20 > I quickly tried it out just now, and IMO while the *functionality* is=20 > there, the usability of devbind is IMO far more friendly: > > - it filters by device types that are of interest to us (driverctl just= =20 > lists all pci devices) > - it prints out user-friendly names, not just PCI addresses > - it lists loaded drivers, but not alternatives etc. like devbind does > - I didn't test this, but I suspect it would allow overriding driver for= =20 > an active NIC > - after my changes, devbind displays NUMA socket, driverctl doesn't :) Yes, that's fair. devbind is more a dev oriented tool. driverctl is=20 really focused on reproducible and persistent driver override (it has=20 a systemd service that will force a rebind of pci devices on reboot). > What we maybe can do for e.g. next release (currently I do have better=20 > things to do if I can help it), is to make devbind a wrapper around=20 > driverctl? This way, we can still keep the usability bells and whistles= =20 > we have, but drop the driver overriding code and leave it to driverctl?= =20 > It seems like that would be a good compromise, with the only downside=20 > being that we'll depend on driverctl being installed. Honestly, I don't think the dependency would be a good idea. Also,=20 driverctl does not have any option to make a driver override temporary.=20 It will persist after reboot which is not what devbind does.