From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Reg DPDK with unsupported NIC Date: Tue, 14 Mar 2017 10:46:22 +0100 Message-ID: <6993622.nn8h5H1WbH@xps13> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, users To: raman geetha gopalakrishnan Return-path: Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id 95E0D3777 for ; Tue, 14 Mar 2017 10:46:24 +0100 (CET) Received: by mail-wm0-f43.google.com with SMTP id n11so59130207wma.0 for ; Tue, 14 Mar 2017 02:46:24 -0700 (PDT) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2017-03-14 14:58, raman geetha gopalakrishnan: > In what way i can still develop DPDK APP with non supported NIC till get > the DPDK NIC. You should check the bottom of this page (section Ohers): http://dpdk.org/doc/nics The simplest is to use the ring PMD which do not require a NIC at all. Or you can try the other solutions (pcap, tap, af_packet).