From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nbfkord-smmo02.seg.att.com (nbfkord-smmo02.seg.att.com [209.65.160.78]) by dpdk.org (Postfix) with ESMTP id A785E101B for ; Tue, 21 Mar 2017 09:19:01 +0100 (CET) Received: from unknown [193.34.186.16] (EHLO webmail.solarflare.com) by nbfkord-smmo02.seg.att.com(mxl_mta-7.2.4-7) with ESMTP id 5f1e0d85.2b12354a1940.446429.00-2453.1141700.nbfkord-smmo02.seg.att.com (envelope-from ); Tue, 21 Mar 2017 08:19:01 +0000 (UTC) X-MXL-Hash: 58d0e1f5777d7822-acfc067df73a2f1f3ec2a770646fc2087ea44231 Received: from unknown [193.34.186.16] (EHLO webmail.solarflare.com) by nbfkord-smmo02.seg.att.com(mxl_mta-7.2.4-7) over TLS secured channel with ESMTP id fe1e0d85.0.446428.00-2312.1141695.nbfkord-smmo02.seg.att.com (envelope-from ); Tue, 21 Mar 2017 08:18:57 +0000 (UTC) X-MXL-Hash: 58d0e1f101f8ea4f-1215d6a6097f784d22984c19130f6576abf18edf Received: from [192.168.38.17] (84.52.89.52) by ukex01.SolarFlarecom.com (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 21 Mar 2017 08:18:29 +0000 To: Ankit Aggarwal , References: From: Andrew Rybchenko Message-ID: Date: Tue, 21 Mar 2017 11:18:24 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [84.52.89.52] X-ClientProxiedBy: ocex03.SolarFlarecom.com (10.20.40.36) To ukex01.SolarFlarecom.com (10.17.10.4) X-TM-AS-Product-Ver: SMEX-11.0.0.1191-8.100.1062-22954.003 X-TM-AS-Result: No--9.929900-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-AnalysisOut: [v=2.1 cv=Ndfgoj34 c=1 sm=1 tr=0 a=8P+NB+fYZDP74ap4g4d9Kw==] X-AnalysisOut: [:17 a=RB3BGLmKESwA:10 a=6Iz7jQTuP9IA:10 a=8rWy6zfcAAAA:8 a] X-AnalysisOut: [=8FRvbaJW1zjaMm8LKYYA:9 a=QEXdDO2ut3YA:10 a=pGLkceISAAAA:8] X-AnalysisOut: [ a=8hxI3BbS-03tE-g0C6gA:9 a=3g0eTJcQ2sKkncwS:21 a=_W_S_7Ve] X-AnalysisOut: [coQA:10 a=YjdVzJdQTyZRADMV7wFX:22 a=6kGIvZw6iX1k4Y-7sg4_:2] X-AnalysisOut: [2] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2015072901)] X-MAIL-FROM: X-SOURCE-IP: [193.34.186.16] Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Solarflare DPDK 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, 21 Mar 2017 08:19:02 -0000 Hi Ankit, (May be users@dpdk.org is a better place for such questions) OpenOnload provides a user-level TCP/IP stack with POSIX interface – transparently runs any Linux sockets binary without requiring any changes to the application. "DPDK is a set of libraries and drivers for fast packet processing. [snip] DPDK is not a networking stack" (quotes from dpdk.org). So they have very different end use-cases. So if end-use case is performing packet processing and/or switching packets between network interfaces then DPDK allows an open API to be used. However, if app needs to terminate TCP or UDP flows then OpenOnload provides a mature TCP/IP stack. We’ve seen good results with applications such as Nginx with OpenOnload. Regards, Andrew. On 03/20/2017 05:22 PM, Ankit Aggarwal wrote: > Hi DPDK Users/devs > > Can you please tell me the benefits of using DPDK over openonload for > solarflare cards? > > Ankit Aggarwal