From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f174.google.com (mail-pg1-f174.google.com [209.85.215.174]) by dpdk.org (Postfix) with ESMTP id 204F21B526 for ; Thu, 22 Nov 2018 20:19:20 +0100 (CET) Received: by mail-pg1-f174.google.com with SMTP id 80so2079368pge.4 for ; Thu, 22 Nov 2018 11:19:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=pedNICtEHi0mzXKhOIchkxd3gRQDoWDculeWxfPYiEw=; b=XTd3r1D8XbZl2+BiyRkCO3DEf9Qku7BFXmKw6pUiYZdYG5c2M9dou1SOYq6CHDbHsy GCbBt/y5KKCNaOAZLWmNhQhLPqwzerpzbywbf19IMgGUy5/EoD0nsR6n8Kkiph9hwiCM a6m+SyligHBiavbbFE7Vxv9Gu1WN8gIBK9DBoU6WE2QuftE4HFTMESGk1AjK+gtupt88 baFilUBsLcBQJplPvN2at742oupeV1iDstyGweiOHaiekAgJkWYjKRVaN4gCdC6W2Qul VJGW3HEiuAImha8Rsnz2AVZhrWg3hZ7uCpuxGMJl4xANysZmwjvMoyrgCERjxXnkP0Pi HFSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=pedNICtEHi0mzXKhOIchkxd3gRQDoWDculeWxfPYiEw=; b=T6iWsIJkhoFpKudQoL7zYqF7LLnPa1U8U/AOvIh02yFaxktjwMHisCNjZmh5hLmufZ wR+zLycrUdPZKDnrCib9LnNAz1cD2zng02RE3L19TolbazFKxAub9Dzv1FVS4yx/JNVW 1MXhiP8k2By3zDCyjtLzXGs20ps+9wgduFXlWWhzMdEL/0MkmgJEN6Qxv9wKD+/NuPge 4LXHkcW43YirCnlWcKFZIW39feVzcgtj0QFbSkSoKoY+d639WWtYUIkYsUMuqgHOAC/J 3J9b0uCsFnZcEHikiFzlSXDX8ceOU+npB9GMdrnxkteMRWN4Arv0ACwWXwBscCIpso2u ggMA== X-Gm-Message-State: AGRZ1gLw+5JUJEy/5V5KK4v9YBSNQlFrBydviftTYP5YgHQ8qZRa2u2o wWp2v9ukvUQbDr/ACIUN5bDLpw== X-Google-Smtp-Source: AJdET5ev7KdH7HL6MtSxNTXAGrWhG0fGFZyyUySmlW0SUsZ2Y9qY9TAI4IvN51QW63A1sUk9fBxaPA== X-Received: by 2002:a62:8145:: with SMTP id t66mr12779501pfd.55.1542914359891; Thu, 22 Nov 2018 11:19:19 -0800 (PST) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id k137sm54283497pfd.56.2018.11.22.11.19.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 22 Nov 2018 11:19:19 -0800 (PST) Date: Thu, 22 Nov 2018 11:19:17 -0800 From: Stephen Hemminger To: Quan Zhou Cc: "users@dpdk.org" , "chengli7@ustc.edu.cn" , "byh0912@mail.ustc.edu.cn" , "xugb@mail.ustc.edu.cn" , "rcy@mail.ustc.edu.cn" , "junyi@nevada.unr.edu" Message-ID: <20181122111917.240bae2a@xeon-e3> In-Reply-To: <5BF66884.3C43CB.24343@ustc.edu.cn> References: <5BF66884.3C43CB.24343@ustc.edu.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] Do dpdk support infiniband ConnectX-3 Pro cards? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2018 19:19:21 -0000 On Thu, 22 Nov 2018 16:27:46 +0800 Quan Zhou wrote: > Hello=EF=BC=8C > I=E2=80=99ve worked on making dpdk running on our infiniband card Mellan= ox ConnectX-3 Pro MT27520 but encountered some problems. I find in dpdk off= icial hardware support list, it only list one ConnectX-3 Pro card which is = an Ethernet card. Here is the hardware support list link: http://doc.dpdk.o= rg/guides/nics/mlx4.html#supported-nics > =E3=80=80=E3=80=80Now I want to ask you whether dpdk supports our card Co= nnectX-3 Pro MT27520, or whether dpdk supports infiniband ConnectX-3 Pro ca= rds.=20 > =E3=80=80=E3=80=80Thanks in advance! >=20 > Regards, > Quan The simplest way to answer that question on your own is to find the pci inf= ormation with lspci. Then lookup card in the tables in the source code. That gives you the defi= nitive answer. Since Mellanox uses bifurcated mode you also have to have the matching Linu= x kernel driver.