From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ferruh.yigit@intel.com>
Received: from mga07.intel.com (mga07.intel.com [134.134.136.100])
 by dpdk.org (Postfix) with ESMTP id 0D827914
 for <dev@dpdk.org>; Fri,  3 Mar 2017 11:51:39 +0100 (CET)
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by orsmga105.jf.intel.com with ESMTP; 03 Mar 2017 02:51:38 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.35,236,1484035200"; d="scan'208";a="231854104"
Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.255.205.116])
 ([10.255.205.116])
 by fmsmga004.fm.intel.com with ESMTP; 03 Mar 2017 02:51:35 -0800
To: Shrikrishna Khare <skhare@vmware.com>, yongwang@vmware.com
References: <1488059989-6930-1-git-send-email-skhare@vmware.com>
 <1488059989-6930-7-git-send-email-skhare@vmware.com>
Cc: dev@dpdk.org, Guolin Yang <gyang@vmware.com>
From: Ferruh Yigit <ferruh.yigit@intel.com>
Message-ID: <75406807-c108-6594-947a-0ce84d1a4d49@intel.com>
Date: Fri, 3 Mar 2017 10:51:34 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <1488059989-6930-7-git-send-email-skhare@vmware.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Subject: Re: [dpdk-dev] [PATCH 6/7] vmxnet3: introduce command to register
 memory region
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Mar 2017 10:51:40 -0000

On 2/25/2017 9:59 PM, Shrikrishna Khare wrote:
> In vmxnet3 version 3, the emulation added support for the vmxnet3 driver
> to communicate information about the memory regions the driver will use
> for rx/tx buffers. The driver can also indicate which rx/tx queue the
> memory region is applicable for. If this information is communicated
> to the emulation, the emulation will always keep these memory regions
> mapped, thereby avoiding the mapping/unmapping overhead for every packet.
> 
> Signed-off-by: Shrikrishna Khare <skhare@vmware.com>
> Signed-off-by: Guolin Yang <gyang@vmware.com>
> Acked-by: Yong Wang <yongwang@vmware.com>
> Acked-by: Jin Heo <heoj@vmware.com>

<...>

> +		PMD_INIT_LOG(INFO,
> +			     "index: %u startPA: %lu  length: %u, rxBits: %x",
> +			     j, mr->startPA, mr->length, mr->rxQueueBits);

Also this gives following build error for 32bit (i686) build:

.../drivers/net/vmxnet3/vmxnet3_ethdev.c: In function
‘vmxnet3_dev_setup_memreg’:
.../drivers/net/vmxnet3/vmxnet3_ethdev.c:564:52: error: format ‘%lu’
expects argument of type ‘long unsigned int’, but argument 6 has type
‘uint64 {aka long long unsigned int}’ [-Werror=format=]
         j, mr->startPA, mr->length, mr->rxQueueBits);
                                                    ^