From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id E8F6D1075 for ; Tue, 14 Mar 2017 10:31:42 +0100 (CET) Received: by mail-wm0-f48.google.com with SMTP id n11so58995478wma.1 for ; Tue, 14 Mar 2017 02:31:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=Z/FWkLHOw/5wc70ozPiSUVOC8iED6INHriMlGRY9ej4=; b=tEUoZB7O75jVtbgBlQbry8pc2fakEovEzc0uO6FcHKFQP+uwL1vBdNLO8TGRcKm74u 2Nr9+a5lU+5OK2SK9vcEoLkLiWyJMZmnSEJolLgF70HGl/mg5sxI2Mi4dsDRGVq1Inj1 ymCEhQHxjHMW7jHSxITUGeatkiISFWq9mezUpgnp4Ku/xFRM/jfLauX1IKsUqKAY3Laf sYpXk8EZ4+9lysLTnCpbhrJb9a0lbp8jOvFjif9H4eBu9MZqcGU1juV3KytJYeSfawE6 L8ihredfP4MPZw1D4qwiCkdOzIgO7l5hCjDpXISbIrdujJg1/Z0UcekERocDjF5RUPy2 fPcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Z/FWkLHOw/5wc70ozPiSUVOC8iED6INHriMlGRY9ej4=; b=hcjsQ2p3oo2qnlixKwq089kz/DFzkHY49AzAiSB+Yu02J08y5ZCqp3AeQgkYmIz7QX FoyzBWLqLdIzWQ7Pz7h8yJRpxcA/jlO6EHH6G+hWf9LwC3JnU+zYlUQBozDJ9FiQ0oZ6 iU9EhYIx3PbyE/JOVxkSTgHXHciZ4fDTBrMhrWBVGM0W06ubGZK4YEun6WA8f6r9U7fp EWw0uEcEIGhSvft9IbyDIL+KSSNnCEWQGUjYLqNC1V4uFblGy3v37PnYg4XnbPImWSHc 8yJq8kSsfUlLqG9XlwRpiR4A8iQEiA3ufrnLQumo+Ite88t9yzghDtA7i/t/V+Sa+Rip 2wDQ== X-Gm-Message-State: AFeK/H3rbrlqRd1guBRUCzlKJR+tFCwNRfVy19m84vK34REaoB5xPoXrvZoJ2jL0QBkdSg== X-Received: by 10.28.216.141 with SMTP id p135mr14680083wmg.71.1489483902301; Tue, 14 Mar 2017 02:31:42 -0700 (PDT) Received: from [192.168.13.1] (51B65A28.dsl.pool.telekom.hu. [81.182.90.40]) by smtp.gmail.com with ESMTPSA id p12sm28556922wrb.46.2017.03.14.02.31.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Mar 2017 02:31:41 -0700 (PDT) To: dev@dpdk.org References: From: =?UTF-8?B?R8OpbWVzIEfDqXph?= Message-ID: <0142a229-7590-9bea-8b4c-5fe0d0774053@gmail.com> Date: Tue, 14 Mar 2017 10:31:40 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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:31:43 -0000 2017-03-14 10:28 keltezéssel, raman geetha gopalakrishnan írta: > Hi , > > Please find my query, Currently i am planning to develop DPDK APP (linux > env). I do not have DPDK supported NIC. Till then i would still like to > develop DPDK APP and want DPDK to use OS interface to TX/RX packets from > NIC. How can i make it? I went through KNI and my understanding is you > cannot use it - is this correct? > > In what way i can still develop DPDK APP with non supported NIC till get > the DPDK NIC. > > Thanks > Raman Hi, My recommendation is to do your development in a KVM VM. DPDK works perfectly with virtio NICs. Geza