All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>,
	Michael Guralnik <michaelgur@mellanox.com>
Subject: [PATCH rdma-next 0/2] Set BlueFlame size based on memory properties
Date: Sun, 20 Oct 2019 09:43:58 +0300	[thread overview]
Message-ID: <20191020064400.8344-1-leon@kernel.org> (raw)

From: Leon Romanovsky <leonro@mellanox.com>

Hi,

Libmlx5 needs real knowledge of BlueFlame size to properly set data
path to leverage performance advantages of BF. However such advantage
is visible in systems which use WC memory. Unfortunately, user space
applications (and libmlx5) can't know if memory is WC or not, so
we rely on in-kernel test to set BF dynamically.

Thanks

Michael Guralnik (2):
  IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines
  IB/mlx5: Test write combining support

 drivers/infiniband/hw/mlx5/gsi.c     |   2 +-
 drivers/infiniband/hw/mlx5/main.c    |  15 +-
 drivers/infiniband/hw/mlx5/mem.c     | 200 +++++++++++++++++++++++++++
 drivers/infiniband/hw/mlx5/mlx5_ib.h |  13 +-
 drivers/infiniband/hw/mlx5/qp.c      |  12 +-
 5 files changed, 229 insertions(+), 13 deletions(-)

--
2.20.1


             reply	other threads:[~2019-10-20  6:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20  6:43 Leon Romanovsky [this message]
2019-10-20  6:43 ` [PATCH rdma-next 1/2] IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines Leon Romanovsky
2019-10-22 19:40   ` Jason Gunthorpe
2019-10-20  6:44 ` [PATCH rdma-next 2/2] IB/mlx5: Test write combining support Leon Romanovsky
2019-10-22 12:35   ` Leon Romanovsky

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=20191020064400.8344-1-leon@kernel.org \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michaelgur@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.