From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Ricardo Leitner Subject: Question on documentation / Mellanox ConnectX-3 Date: Tue, 3 Apr 2018 14:59:38 -0300 Message-ID: <20180403175938.GA23889@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Timothy Redaelli To: dev@dpdk.org Return-path: Received: from mail-qk0-f176.google.com (mail-qk0-f176.google.com [209.85.220.176]) by dpdk.org (Postfix) with ESMTP id 2941C1B83C for ; Tue, 3 Apr 2018 19:59:44 +0200 (CEST) Received: by mail-qk0-f176.google.com with SMTP id s78so19555579qkl.8 for ; Tue, 03 Apr 2018 10:59:44 -0700 (PDT) Content-Disposition: inline List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, http://docs.openvswitch.org/en/latest/howto/dpdk/ says: Some NICs (i.e. Mellanox ConnectX-3) have only one PCI address associated with multiple ports. Using a PCI device like above won’t work. Instead, below usage is suggested: $ ovs-vsctl add-port br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk \ options:dpdk-devargs="class=eth,mac=00:11:22:33:44:55:01" $ ovs-vsctl add-port br0 dpdk-p1 -- set Interface dpdk-p1 type=dpdk \ options:dpdk-devargs="class=eth,mac=00:11:22:33:44:55:02" But these MACs are 7 bytes long. Seems the idea was to mention the two incremental MAC addresses that the ports have, and thus the ':55' should have been removed from there, right? Reading the code, it doesn't seem prepared to handle the extra byte in any (special) way. Marcelo