From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by dpdk.org (Postfix) with ESMTP id AAFD82E8A for ; Mon, 10 Mar 2014 16:49:22 +0100 (CET) Received: by mail-pa0-f47.google.com with SMTP id lj1so7418122pab.34 for ; Mon, 10 Mar 2014 08:50:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=Q3wc1+2M+NY81II9fofAEFfUdeeOTnRDtkIOW4igwHs=; b=ev1ko3k77hOH8U20HXV8qzQs/Oq63GD8boI27SH3aohSot/+hRjvWCCThFR/IcDdmd luL9uAefLGzwg5nNL4Dpc0mPu9xEIDdQN+Td4pSZO63NRTbl8dN//fct8vL1q6rXHoX/ Bbo6PTyAQnAlxVE500Um1qTM9W06DUrsJWaLTMHImbtqzV+FrMleaH5Attw6A0GIsemm g3XxoR064Z3x+2LS4gn2nCEjhzD20ZwtJwUdBjg9kohNTWF7s2nsB+7jPfplZem48Qi0 iDttBV9OwyVV8kxDPSQg5hM6SxwKPaHC8kzWPLEthWsK9/bQ16jsk1eBLic9cpwa/wk1 DlZw== X-Gm-Message-State: ALoCoQksL80JARvMQ42G8Dgaxvl9s+sXtWmZx2k6g2b8X9mJbUO7XezZL2HpKJHWthjBeP63dok8 X-Received: by 10.68.229.68 with SMTP id so4mr34572441pbc.110.1394466651656; Mon, 10 Mar 2014 08:50:51 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51]) by mx.google.com with ESMTPSA id eb5sm85594438pad.22.2014.03.10.08.50.50 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 10 Mar 2014 08:50:51 -0700 (PDT) Date: Mon, 10 Mar 2014 08:50:48 -0700 From: Stephen Hemminger To: Prashant Upadhyaya Message-ID: <20140310085048.71a49faf@nehalam.linuxnetplumber.net> In-Reply-To: References: X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Which vmxnet3 pmd is to be used in dpdk 1.6.x? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Mar 2014 15:49:23 -0000 On Mon, 10 Mar 2014 13:30:48 +0530 Prashant Upadhyaya wrote: > Hi Srini, > > Thanks, I could also make it work, thanks to your cue ! > > Now then, this multi-segment not being supported in vmxnet3 driver is a big party-pooper for me. Unfortunately in my usecase, I do indeed make heavy use of multisegment buffers for sending out the data, so my usecase has failed and I will have to fix that. > > Also, can you please adivse how much is the max data rates you have been able to achieve with one vmxnet3 10G port. > > Thanks a lot for the advice once again. > > Regards > -Prashant I am integrating our driver with the 1.6.1 DPDK driver. We support multi-segment, if you want I will backport that feature first.