From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by dpdk.org (Postfix) with ESMTP id D347F7E0B for ; Thu, 30 Oct 2014 16:08:12 +0100 (CET) Received: by mail-wg0-f54.google.com with SMTP id m15so4530068wgh.27 for ; Thu, 30 Oct 2014 08:17:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=EKAFvt7eikDE36tJlaqXHhQvpM11SqpKVVOfGMWxuWQ=; b=esEJRsZY7K0ilJApYTyf7eDdGxpLfnL9NhwM3xQlFGO64l6SKdGJJlWHC5x8k/aL4+ OU4/2bhbjsRbbzhRRR99FFPPZ6E77uxPxLhE1QDHs5AzuhGv41kvWj4AbsmKBq1ZHA4x 123bbogoOwPGRzAYvrXVRcgEu6cRb9l1DdY5l5YsoYP8t+yTthhsdq1WuHISslwD9QLx wKb4t6ROQmuUNn9+zrHjWeh4vJOrBtAzSZWIlQ8xilAlUN88lAlXX+IDUnidOqzEwynz ewh21lFcQeVa1NLKu/CSG4IQk1+n3EVBHdgSf0hn0j0bPuJrkfHOh/W0Xk7RRsDSIrle FteA== X-Gm-Message-State: ALoCoQlLAfKaSZdmYzEPBeuzXQQZ47A1UQi3JqEhv4yYwg8pq7bEUKl/0bCEE+XpEzeVLIXLxTAD X-Received: by 10.180.12.143 with SMTP id y15mr21232078wib.35.1414682229276; Thu, 30 Oct 2014 08:17:09 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id s8sm9027785wjx.9.2014.10.30.08.17.07 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Oct 2014 08:17:08 -0700 (PDT) From: Thomas Monjalon To: Yan Freedland Date: Thu, 30 Oct 2014 16:16:49 +0100 Message-ID: <1646262.f1p7vlGK46@xps13> Organization: 6WIND User-Agent: KMail/4.14.2 (Linux/3.17.1-1-ARCH; KDE/4.14.2; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] working with VMXNET3 driver in a "NIC Connected to a vSwitch" setup on VMware 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: Thu, 30 Oct 2014 15:08:13 -0000 2014-10-29 17:48, Yan Freedland: > I am interested in working with VMXNET3 driver in a NIC - vSwitch > fashion on VMware. > > For that purpose I did the following: > > > 1. On my VMware VM I compiled the driver and loaded it as described > in http://dpdk.org/doc/vmxnet3-usermap > > 2. Using vSphere client I created 2 network adapters of VMXNET3 type > and assigned a relevant port-group to allow a client-server connectivity > later on. > > My question is how should I pick and bind ports to the driver. > Should I use dpdk_nic_bind.py script as I did with igb_uio ? > if yes, how may I find the port addresses ? > > Besides should I do something special in environment initialization > (e.g. ports, memory, etc...) that I didn't do for virtio or ixgbe ? > For instance it looks logical to me to use vmxnet3-usermap in my commands > (e.g. dpdk_nic_bind.py --bind= vmxnet3-usermap ) instead > of igb_uio but I don't really know how. Just follow the documentation: http://dpdk.org/doc/vmxnet3-usermap This implementation doesn't use uio and doesn't need dpdk_nic_bind.py. -- Thomas