linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Michal Kalderon <michal.kalderon@marvell.com>
Cc: <dledford@redhat.com>, <aelior@marvell.com>, <ybason@marvell.com>,
	<mkalderon@marvell.com>, <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v3 rdma-next 0/2] RDMA/qedr: Add EDPM kernel-user flags for feature compatibility
Date: Thu, 16 Jul 2020 16:07:58 -0300	[thread overview]
Message-ID: <20200716190758.GA2682412@nvidia.com> (raw)
In-Reply-To: <20200707063100.3811-1-michal.kalderon@marvell.com>

On Tue, Jul 07, 2020 at 09:30:58AM +0300, Michal Kalderon wrote:
> The two patches in this series are related to the EDPM feature.
> EDPM is a hw feature for improving latency under certain conditions.
> 
> Related rdma-core pull request #786
> https://github.com/linux-rdma/rdma-core/pull/786
> 
> Signed-off-by: Michal Kalderon <michal.kalderon@marvell.com>
> 
> Changes from v2
> Remove mis-use of !! when checking if a flag is set.
> 
> Changes from v1
> Add explicit padding to struct qedr_alloc_ucontext_resp in qedr-abi.h
> 
> Michal Kalderon (2):
>   RDMA/qedr: Add EDPM mode type for user-fw compatibility
>   RDMA/qedr: Add EDPM max size to alloc ucontext response

applied to for-next, thanks

Jason

      parent reply	other threads:[~2020-07-16 19:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07  6:30 [PATCH v3 rdma-next 0/2] RDMA/qedr: Add EDPM kernel-user flags for feature compatibility Michal Kalderon
2020-07-07  6:30 ` [PATCH v3 rdma-next 1/2] RDMA/qedr: Add EDPM mode type for user-fw compatibility Michal Kalderon
2020-07-07  6:31 ` [PATCH v3 rdma-next 2/2] RDMA/qedr: Add EDPM max size to alloc ucontext response Michal Kalderon
2020-07-16 17:10   ` Jason Gunthorpe
2020-07-16 18:17     ` Michal Kalderon
2020-07-16 18:57       ` Jason Gunthorpe
2020-07-16 19:05         ` [EXT] " Michal Kalderon
2020-07-16 19:07 ` Jason Gunthorpe [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=20200716190758.GA2682412@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=aelior@marvell.com \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michal.kalderon@marvell.com \
    --cc=mkalderon@marvell.com \
    --cc=ybason@marvell.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).