All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@mellanox.com>,
	Michael Guralnik <michaelgur@mellanox.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH rdma-next v1] IB/mlx5: Test write combining support
Date: Mon, 28 Oct 2019 16:07:15 +0200	[thread overview]
Message-ID: <20191028140715.GJ5146@unreal> (raw)
In-Reply-To: <CAJ3xEMiV-ufcJST70i7J1UOkmx2tV=kc77GiRYKX8Yq4UyXpZQ@mail.gmail.com>

On Mon, Oct 28, 2019 at 03:38:13PM +0200, Or Gerlitz wrote:
> On Sun, Oct 27, 2019 at 8:29 AM Leon Romanovsky <leon@kernel.org> wrote:
> >
> > From: Michael Guralnik <michaelgur@mellanox.com>
> >
> > Add a test in mlx5_ib initialization process to test whether
> > write-combining is supported on the machine.
> > The test will run as part of the enable_driver callback to ensure that
> > the test runs after the device is setup and can create and modify the
> > QP needed, but runs before the device is exposed to the users.
> >
> > The test opens UD QP and posts NOP WQEs, the WQE written to the BlueFlame
> > is differnet from the WQE in memory, requesting CQE only on the BlueFlame
>
> nit: different

Thanks, Jason/Doug should I resend?

>
> > WQE. By checking whether we received a completion on one of these WQEs we
> > can know if BlueFlame succeeded and whether write-combining is supported.
> >
> > Change reporting of BlueFlame support to be dependent on write-combining
> > support.

  reply	other threads:[~2019-10-28 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-27  6:22 [PATCH rdma-next v1] IB/mlx5: Test write combining support Leon Romanovsky
2019-10-28 13:38 ` Or Gerlitz
2019-10-28 14:07   ` Leon Romanovsky [this message]
2019-10-28 17:59     ` Jason Gunthorpe
2019-10-31 19:02 ` Jason Gunthorpe

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=20191028140715.GJ5146@unreal \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=gerlitz.or@gmail.com \
    --cc=jgg@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.