From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <3chas3@gmail.com> Received: from mail-yk0-f173.google.com (mail-yk0-f173.google.com [209.85.160.173]) by dpdk.org (Postfix) with ESMTP id 3F9FD8E5D for ; Tue, 10 Nov 2015 19:51:49 +0100 (CET) Received: by ykdr82 with SMTP id r82so9597097ykd.3 for ; Tue, 10 Nov 2015 10:51:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=4dq9x0vNTc6MxVBsfsXnQsPnB3lsNkABe6+ktoumk/w=; b=wGWC3xvgc1j5vkHY3TK4MXeTNObURix/vUPD965l0+Hm62u1jCSToKWjJreVL1nP1Z melu9y283WSkVnZP77Q4OSze+iremmhaCH351e7P+kwz02kUqalLi3iPOjgdSaVn0kGQ gE8vQCU1zHlaDGGsTJdVUcAbrHReSVKP3NZX53+JiFjTDSLPFJMcjPUlDce1zHmlZHtH 9BJD+P+lofVlMCLgGu1mWupcuvHUMdkXiLf4Ja/P1xDoyLwktfO5n1CPLWKw8XScOkWc naw/wpzRP7yvT5WI0jPzDCzxWNAjP9bJv28pKDb34AsnNn0GwNmaYlaDnUiUZ7DORvGB nmgg== X-Received: by 10.129.148.3 with SMTP id l3mr4489459ywg.30.1447181508662; Tue, 10 Nov 2015 10:51:48 -0800 (PST) Received: from foobar.home (pool-71-163-182-126.washdc.fios.verizon.net. [71.163.182.126]) by smtp.googlemail.com with ESMTPSA id i201sm5742365ywe.10.2015.11.10.10.51.47 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Nov 2015 10:51:47 -0800 (PST) Message-ID: <1447181507.2645.9.camel@gmail.com> From: "Charles (Chas) Williams" <3chas3@gmail.com> To: Stephen Hemminger Date: Tue, 10 Nov 2015 13:51:47 -0500 In-Reply-To: <20151105112358.6cec995f@xeon-e3> References: <1443798007-20122-1-git-send-email-3chas3@gmail.com> <561CFDDB.90601@6wind.com> <1444830094.3494.59.camel@gmail.com> <7145730.ihAL5VqqiH@xps13> <1446741544.1777.3.camel@gmail.com> <20151105112358.6cec995f@xeon-e3> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 (3.12.11-1.fc21) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name 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: Tue, 10 Nov 2015 18:51:49 -0000 On Thu, 2015-11-05 at 11:23 -0800, Stephen Hemminger wrote: > On Thu, 05 Nov 2015 11:39:04 -0500 > "Charles (Chas) Williams" <3chas3@gmail.com> wrote: > > > On Wed, 2015-11-04 at 23:40 +0100, Thomas Monjalon wrote: > > > 2015-10-14 09:41, Charles Williams: > > > > On Tue, 2015-10-13 at 14:49 +0200, Olivier MATZ wrote: > > > > > For PCI devices that have several interfaces (I think it's the case for > > > > > some Mellanox boards), maybe we should not store the interface name? > > > > > > > > I am not sure what you mean here. If a device has multiple ethernet > > > > interfaces, then it should a have seperate PCI device address space for > > > > each interface (I dont know of any DPDK drivers that don't make this > > > > assumption as well). > > > > > > mlx4 and cxgbe? > > > > OK, I see now. I don't know of a way to tell if a device has multiple > > ports just from the pci vendor/device id without maintaining some > > sort of table. > > > > Do these devices have multiple interfaces listed in their > > /sys/devices/.../net diretory? If so, matching one of the listed > > interfaces can just blacklist the whole device similar to blacklisting > > by the device id. > > Devices with multiple ports are supposed to report the port via /sys/class/net/xxx/portid But I want to find the ports associated by the PCI devices. > But you aren't going to be able to blacklist only one port of these devices. > The two drivers would be fighting over registers and IRQ management. > Plus kernel bind/unbind is by PCI id. I understand that. Blacklisting an interface on a multiple port device would be essentially the same as blacklist by the PCI device id. You can't split the PCI device. I just need to find the list of ports associated with a single PCI device.