From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=kNkljd2y7Enw3YT+UZ1Nyp6uEyuLdriX/Y4LVlHHinc=; b=vQDYIKfW0V65R948BPhZE2/bHJDuvxacRw3VUAMuW7RrlkaEq4WyVPSLK4OSbvFHYc 0PWMJaauamQ1mKQrughUAUjixvci2f7pLTf7a60EUi2E11IN7IBbZWCNdBoQK4GnxVys lCx23YOpODBiuCqSZKPoBn8+XOY3l0PtqjwJ2cuj5AVmv8HT8oWrF8NnC8v8Q4q55Dzf g1OVMCLz+Vu0aHPTMC529/3kROGmAGjf3ilybP5q5wxSsdz+gkugqDhF+EQFXC9y82IU X1oJVhdKmHpnuuy9cLm2TEYAu+ZClXfIchl7GxCqnvNF/yoG9P2HNoS3Rs9eXqdjcqF+ 7yOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=kNkljd2y7Enw3YT+UZ1Nyp6uEyuLdriX/Y4LVlHHinc=; b=IyvEc13QWRUBLxDOZcUXKhQicR718LS+bHhs6Sd5I3Ah7ZRfYuO1n5zj/2LzWKNxTx 5weOM1AIdyUkGa4gKiBvTU8AJir6kslrhCji5qe7fLK2TYgDV5pfHxt5PmtKh+aeuDa+ fRm/V9rks63LKrNnEwYnMop5KCP6Rr8iOhpPq0ARbFNXGx09+DX1WDO0VHMLPnrOY7eH zSHN+b2MT72ARiJ9BkKmldhmponrB8iVrNCQQw3dTsEoQM2L92ZoPHuWOEBVTUVwcDpT sDcN6hXch/SCnB4yIfeU/go3R9Tw+0TJsZbbjVJ2rZUUV1psSkNLykXhsnfPy478fAQ6 eIHw== X-Gm-Message-State: AFeK/H2bqUBQbeowtfs/txghZd7cVeVkLMwrdQ90C0lFAVPGGT3cTmiXLNUbaxGIPkCmNLAw X-Received: by 10.28.57.131 with SMTP id g125mr13284509wma.33.1489484784168; Tue, 14 Mar 2017 02:46:24 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id z88sm28543524wrb.26.2017.03.14.02.46.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Mar 2017 02:46:23 -0700 (PDT) From: Thomas Monjalon To: raman geetha gopalakrishnan Cc: dev@dpdk.org, users Date: Tue, 14 Mar 2017 10:46:22 +0100 Message-ID: <6993622.nn8h5H1WbH@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Reg DPDK with unsupported NIC X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2017 09:46:24 -0000 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).