From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 76363201 for ; Tue, 25 Jul 2017 16:06:58 +0200 (CEST) Received: by mail-wm0-f46.google.com with SMTP id c184so57413376wmd.0 for ; Tue, 25 Jul 2017 07:06:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=oYZKQPZ3qfUsnyHCcU9yoXg61x/s/w2kkxWNI4Dfqrk=; b=Tid1gUaqggWK94To9sqq+CKXtXTme/xPXT1vKJ7k/tBZ9GvtOOiYLAUqvDS2lrl0OZ E2FeMxQm1A3snXwFHTuGC5leqnh6hvWoSoFx1MAzwGtl5QAXogx/ZeeNX+JODHUv1skl PPbSS1qgU8NbGyJTRjsXrKxFtnuZyAqXlYh0HncgZ7IuTyKLby58aOOyG8kF1ylsV3OB XWWkCmRc/XUXBUJor6r4PSyIBb2Hxn2aYliwMuEhm/+ucBLCqbFZ4DjLy++hN1lXyntz Y4zEiJss3O56rFtiO4QqkRM5aaI2/OzEbEzf25Bp7ZBTB0XAmf2E/kxnc+o2LZzHSBVT b77Q== 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:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=oYZKQPZ3qfUsnyHCcU9yoXg61x/s/w2kkxWNI4Dfqrk=; b=A2kes7c0tOy9kN0oXQ4yoMlGjyUprmfRZEoMTUHJQcpzpbLcx5e0JWD52vy+h3xbXt 1aVRZj2ThrELcpKnsmQDpHZFFSMlX9z8FuODXbe5T9fiztW5rA+5iIjS+wzWSmQy0IMV veIRjwv9INImLQoq73gL+qHUhLEO6kHowY7gSskTA16h9QiVb0xSNWko623faYmSBXR0 zIz7C6ECQMv1crEwQnqXcqKbGwGoLO2jmyovid3DxoV8Pwd/rAlZOuaXBidGFFGk4Hj+ 09fp8S0ZRjJZM0ZsSydfikhTuTHWWm8LY6e3ca091ZVfzCoETVJ8mekEXoq1ze8Hfczi 3mRw== X-Gm-Message-State: AIVw112TDaHfbCmjUOralZdzQ7o7EC5CPDoUnq/G4t9FN8KPoh9+9pn1 CAl71398rVGMthq4 X-Received: by 10.28.47.67 with SMTP id v64mr8116172wmv.84.1500991618038; Tue, 25 Jul 2017 07:06:58 -0700 (PDT) Received: from 6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id d69sm9492102wmd.23.2017.07.25.07.06.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Jul 2017 07:06:57 -0700 (PDT) Date: Tue, 25 Jul 2017 16:06:48 +0200 From: Adrien Mazarguil To: zhilong zheng Cc: users@dpdk.org Message-ID: <20170725140648.GN19852@6wind.com> References: <6AEDAD78-67AD-49D7-A3AD-6D3B950B9695@gmail.com> <20170724182026.GI19852@6wind.com> <468DB57F-35C6-4499-8D66-6179B530F275@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <468DB57F-35C6-4499-8D66-6179B530F275@gmail.com> Subject: Re: [dpdk-users] low Tx throughputs in DPDK with Mellanox ConnectX-3 card 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: Tue, 25 Jul 2017 14:06:58 -0000 Hi Zhilong, On Tue, Jul 25, 2017 at 09:20:38PM +0800, zhilong zheng wrote: > Hi Adrien, > > Thanks for your reply and suggestion. I change the packet size to 128B, it can generate ~34Gbps and ~40Gbps while to 256B and larger. OK, looks like it scales properly, I think you cannot get much more than this with small packets. > > 在 2017年7月25日，02:20，Adrien Mazarguil 写道： > > > > Hi Zhilong, > > > > On Sat, Jul 22, 2017 at 12:05:51AM +0800, zhilong zheng wrote: > >> Hi all, > >> > >> I have some problem when generating packets to the Mellanox ConnectX-3 dual 40G ports card from the latest pktgen-dpdk. > >> > >> The problem is that it can only generate ~22Gbps per port (actually I just use one port.), not saturating the 40G port. This server has two 12-cores E5-2650 v4 @2.20GHz cpus and 128G 2400MHz DDR4 memory. The DPDK version is 16.11. > >> > >> This is the driver bound to the NIC: 0000:81:00.0 'MT27500 Family [ConnectX-3]' if=p6p1,p6p2 drv=mlx4_core unused= > >> I guess that it’s the problem of driver. The document shows the driver name should be librte_pmd_mlx4 (url: http://dpdk.org/doc/guides/nics/mlx4.html ), however when completing installation, it’s bound to mlx4_core. > > > > It's OK, mlx4_core is the name of the kernel driver while librte_pmd_mlx4 is > > that of the DPDK driver. There is no librte_pmd_mlx4 kernel module, see > > blurb about prerequisites [1]. > > > >> Any clue about this problem? And whether it’s caused by the driver or others? > > > > Depending on packet size and other configuration settings, you may have hit > > the maximum packet rate, these devices cannot reach line rate with 64-byte > > packets for instance. > > > > [1] http://dpdk.org/doc/guides/nics/mlx4.html#prerequisites > > > > -- > > Adrien Mazarguil > > 6WIND > -- Adrien Mazarguil 6WIND