DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
	Mordechay Haimovsky <motih@mellanox.com>
Cc: Yongseok Koh <yskoh@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: add support for 32bit systems
Date: Wed, 18 Jul 2018 09:08:48 +0100	[thread overview]
Message-ID: <f590e293-47e6-b60c-321c-9ba81c64a497@intel.com> (raw)
In-Reply-To: <DB7PR05MB44260BBDDA22AED194C56DF5C3580@DB7PR05MB4426.eurprd05.prod.outlook.com>

On 7/13/2018 7:16 AM, Shahaf Shuler wrote:
> 
> Thursday, July 12, 2018 3:02 PM, Mordechay Haimovsky:
>> Subject: [PATCH v3] net/mlx5: add support for 32bit systems
>>
>> This patch adds support for building and running mlx5 PMD on 32bit systems
>> such as i686.
>>
>> The main issue to tackle was handling the 32bit access to the UAR as quoted
>> from the mlx5 PRM:
>> QP and CQ DoorBells require 64-bit writes. For best performance, it is
>> recommended to execute the QP/CQ DoorBell as a single 64-bit write
>> operation. For platforms that do not support 64 bit writes, it is possible to
>> issue the 64 bits DoorBells through two consecutive writes, each write 32
>> bits, as described below:
>> * The order of writing each of the Dwords is from lower to upper
>>   addresses.
>> * No other DoorBell can be rung (or even start ringing) in the midst  of an on-
>> going write of a DoorBell over a given UAR page.
>> The last rule implies that in a multi-threaded environment, the access to a
>> UAR page (which can be accessible by all threads in the process) must be
>> synchronized (for example, using a semaphore) unless an atomic write of 64
>> bits in a single bus operation is guaranteed. Such a synchronization is not
>> required for when ringing DoorBells on different UAR pages.
>>
>> Signed-off-by: Moti Haimovsky <motih@mellanox.com>
> 
> Applied to next-net-mlx (again), thanks. 
> 
> Guidelines for 32b compilation and testing:
> 1. fetch the latest rdma-core from github. Make sure you have commit "708c8242 mlx5: Fix compilation on 32 bit systems when sse3 is on"
> 2. compile rdma-core for 32b by
> 	mkdir build32
> 	cd build32
> 	CFLAGS="-Werror -m32" cmake -GNinja .. -DENABLE_RESOLVE_NEIGH=0 -DIOCTL_MODE=both (approach taken from rdma-core travis build https://github.com/linux-rdma/rdma-core/blob/master/buildlib/travis-build#L20) 
> 	Ninja (or ninja-build)
> 3. compile and run DPDK against build32 directory

I have confirmed the 32bit build with gcc, thanks for the update.

Only with 32bit ICC getting following errors [1] related to the #pragma usage.

[1]
.../dpdk/drivers/net/mlx5/mlx5_prm.h(14): error #2282: unrecognized GCC pragma
  #pragma GCC diagnostic ignored "-Wpedantic"
                         ^

      reply	other threads:[~2018-07-18  8:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28  7:12 [dpdk-dev] [PATCH] " Moti Haimovsky
2018-07-02  7:05 ` Shahaf Shuler
2018-07-02 10:39   ` Mordechay Haimovsky
2018-07-02 11:11 ` [dpdk-dev] [PATCH v2] " Moti Haimovsky
2018-07-02 20:59   ` Yongseok Koh
2018-07-03 12:03     ` Shahaf Shuler
2018-07-04 13:48   ` Ferruh Yigit
2018-07-05 10:09     ` Mordechay Haimovsky
2018-07-05 11:27       ` Ferruh Yigit
2018-07-11 12:22         ` Shahaf Shuler
2018-07-05 17:07       ` Mordechay Haimovsky
2018-07-05 17:49         ` Ferruh Yigit
2018-07-09  7:23           ` Shahaf Shuler
2018-07-08 17:04     ` Mordechay Haimovsky
2018-07-12 12:01   ` [dpdk-dev] [PATCH v3] " Moti Haimovsky
2018-07-13  6:16     ` Shahaf Shuler
2018-07-18  8:08       ` Ferruh Yigit [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f590e293-47e6-b60c-321c-9ba81c64a497@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=motih@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=yskoh@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).