linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Gal Pressman <galpress@amazon.com>
Cc: Doug Ledford <dledford@redhat.com>,
	linux-rdma@vger.kernel.org,
	Alexander Matushevsky <matua@amazon.com>,
	Shadi Ammouri <sammouri@amazon.com>,
	Yossi Leybovich <sleybo@amazon.com>
Subject: Re: [PATCH for-next v3 3/4] RDMA/efa: User/kernel compatibility handshake mechanism
Date: Wed, 22 Jul 2020 08:55:48 -0300	[thread overview]
Message-ID: <20200722115548.GH25301@ziepe.ca> (raw)
In-Reply-To: <20200721133049.74349-4-galpress@amazon.com>

On Tue, Jul 21, 2020 at 04:30:48PM +0300, Gal Pressman wrote:
> Introduce a mechanism that performs an handshake between the userspace
> provider and kernel driver which verifies that the user supports all
> required features in order to operate correctly.
> 
> The handshake verifies the needed functionality by comparing the
> reported device caps and the provider caps. If the device reports a
> non-zero capability the appropriate comp mask is required from the
> userspace provider in order to allocate the context.
> 
> Reviewed-by: Shadi Ammouri <sammouri@amazon.com>
> Reviewed-by: Yossi Leybovich <sleybo@amazon.com>
> Signed-off-by: Gal Pressman <galpress@amazon.com>
>  drivers/infiniband/hw/efa/efa_verbs.c | 49 +++++++++++++++++++++++++++
>  include/uapi/rdma/efa-abi.h           | 10 ++++++
>  2 files changed, 59 insertions(+)
> 
> diff --git a/drivers/infiniband/hw/efa/efa_verbs.c b/drivers/infiniband/hw/efa/efa_verbs.c
> index 26102ab333b2..7ca40df81ee5 100644
> +++ b/drivers/infiniband/hw/efa/efa_verbs.c
> @@ -1501,11 +1501,48 @@ static int efa_dealloc_uar(struct efa_dev *dev, u16 uarn)
>  	return efa_com_dealloc_uar(&dev->edev, &params);
>  }
>  
> +#define EFA_CHECK_COMP(_dev, _comp_mask, _attr, _mask)                         \
> +	(!(_dev)->dev_attr._attr || ((_comp_mask) & (_mask)))
> +
> +#define DEFINE_COMP_HANDSHAKE(_dev, _comp_mask, _attr, _mask)                  \
> +	{                                                                      \
> +		.attr = #_attr,                                                \
> +		.check_comp = EFA_CHECK_COMP(_dev, _comp_mask, _attr, _mask)   \
> +	}
> +
> +int efa_user_comp_handshake(const struct ib_ucontext *ibucontext,
> +			    const struct efa_ibv_alloc_ucontext_cmd *cmd)
> +{
> +	struct efa_dev *dev = to_edev(ibucontext->device);
> +	int i;
> +	struct {
> +		char *attr;
> +		bool check_comp;
> +	} user_comp_handshakes[] = {
> +		DEFINE_COMP_HANDSHAKE(dev, cmd->comp_mask, max_tx_batch,
> +				      EFA_ALLOC_UCONTEXT_CMD_COMP_TX_BATCH),
> +		DEFINE_COMP_HANDSHAKE(dev, cmd->comp_mask, min_sq_depth,
> +				      EFA_ALLOC_UCONTEXT_CMD_COMP_MIN_SQ_WR),
> +	};

This seems like a very expensive construct

Why have the array at all? Just list the macros and have them jump to
err

Jason

  reply	other threads:[~2020-07-22 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 13:30 [PATCH for-next v3 0/4] Add support for 0xefa1 device Gal Pressman
2020-07-21 13:30 ` [PATCH for-next v3 1/4] RDMA/efa: Expose maximum TX doorbell batch Gal Pressman
2020-07-21 13:30 ` [PATCH for-next v3 2/4] RDMA/efa: Expose minimum SQ size Gal Pressman
2020-07-21 13:30 ` [PATCH for-next v3 3/4] RDMA/efa: User/kernel compatibility handshake mechanism Gal Pressman
2020-07-22 11:55   ` Jason Gunthorpe [this message]
2020-07-22 12:04     ` Gal Pressman
2020-07-22 12:08       ` Jason Gunthorpe
2020-07-22 12:13         ` Gal Pressman
2020-07-22 12:30           ` Jason Gunthorpe
2020-07-21 13:30 ` [PATCH for-next v3 4/4] RDMA/efa: Add EFA 0xefa1 PCI ID Gal Pressman

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=20200722115548.GH25301@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=dledford@redhat.com \
    --cc=galpress@amazon.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=matua@amazon.com \
    --cc=sammouri@amazon.com \
    --cc=sleybo@amazon.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).