DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>,
	Mordechay Haimovsky <motih@mellanox.com>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Saleh Alsouqi <salehals@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: add support for 32bit systems
Date: Tue, 3 Jul 2018 12:03:27 +0000	[thread overview]
Message-ID: <DB7PR05MB4426C0C4BEC7F53A989C73D8C3420@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <5AC8C229-F593-479F-BA0E-4BFD7A9C3060@mellanox.com>

Tuesday, July 3, 2018 12:00 AM, Yongseok Koh:
> Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: add support for 32bit systems
> 
> 
> > On Jul 2, 2018, at 4:11 AM, Moti Haimovsky <motih@mellanox.com> wrote:
> >
> > 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>
> > ---
> Acked-by: Yongseok Koh <yskoh@mellanox.com>

Applied to next-net-mlx, thanks. 

> 
> Thanks

  reply	other threads:[~2018-07-03 12:03 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 [this message]
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

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=DB7PR05MB4426C0C4BEC7F53A989C73D8C3420@DB7PR05MB4426.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=motih@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=salehals@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).