From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Ram Amrani <Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Ariel.Elior-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org,
Michal.Kalderon-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH for-next 1/2] RDMA/qedr: Notify user application if DPM is supported
Date: Mon, 19 Jun 2017 09:55:53 -0600 [thread overview]
Message-ID: <20170619155553.GB10188@obsidianresearch.com> (raw)
In-Reply-To: <1497790871-23945-2-git-send-email-Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
On Sun, Jun 18, 2017 at 04:01:10PM +0300, Ram Amrani wrote:
> Direct Packet Mode support may be disabled, e.g, due to limited BAR
> resources. Notifying the user application prevents wasting cycles
> on attempting to send these kind of packets.
>
> Signed-off-by: Ram Amrani <Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
> drivers/infiniband/hw/qedr/main.c | 1 +
> drivers/infiniband/hw/qedr/qedr.h | 2 ++
> drivers/infiniband/hw/qedr/verbs.c | 6 ++++++
> include/uapi/rdma/qedr-abi.h | 1 +
> 4 files changed, 10 insertions(+)
>
> diff --git a/drivers/infiniband/hw/qedr/main.c b/drivers/infiniband/hw/qedr/main.c
> index 6a72095..d228718 100644
> +++ b/drivers/infiniband/hw/qedr/main.c
> @@ -778,6 +778,7 @@ static struct qedr_dev *qedr_add(struct qed_dev *cdev, struct pci_dev *pdev,
> if (rc)
> goto init_err;
>
> + dev->user_dpm_enabled = dev_info.user_dpm_enabled;
> dev->num_hwfns = dev_info.common.num_hwfns;
> dev->rdma_ctx = dev->ops->rdma_get_rdma_ctx(cdev);
>
> diff --git a/drivers/infiniband/hw/qedr/qedr.h b/drivers/infiniband/hw/qedr/qedr.h
> index aa08c76..42af9b6 100644
> +++ b/drivers/infiniband/hw/qedr/qedr.h
> @@ -158,6 +158,8 @@ struct qedr_dev {
> struct qedr_qp *gsi_qp;
>
> unsigned long enet_state;
> +
> + u8 user_dpm_enabled;
> };
>
> #define QEDR_MAX_SQ_PBL (0x8000)
> diff --git a/drivers/infiniband/hw/qedr/verbs.c b/drivers/infiniband/hw/qedr/verbs.c
> index 17685cf..6a0acfa 100644
> +++ b/drivers/infiniband/hw/qedr/verbs.c
> @@ -335,6 +335,9 @@ static bool qedr_search_mmap(struct qedr_ucontext *uctx, u64 phy_addr,
> return found;
> }
>
> +#define QEDR_LIB_UCXT_SUPPORT(field, udata, value) \
> + ((offsetof(struct qedr_alloc_ucontext_resp, field) < udata->outlen) ? \
> + (value) : 0)
> struct ib_ucontext *qedr_alloc_ucontext(struct ib_device *ibdev,
> struct ib_udata *udata)
> {
> @@ -368,6 +371,9 @@ struct ib_ucontext *qedr_alloc_ucontext(struct ib_device *ibdev,
>
> memset(&uresp, 0, sizeof(uresp));
>
> + uresp.dpm_enabled = QEDR_LIB_UCXT_SUPPORT(dpm_enabled, udata,
> + dev->user_dpm_enabled);
> +
> uresp.db_pa = ctx->dpi_phys_addr;
> uresp.db_size = ctx->dpi_size;
> uresp.max_send_wr = dev->attr.max_sqe;
> diff --git a/include/uapi/rdma/qedr-abi.h b/include/uapi/rdma/qedr-abi.h
> index 75c270d..2684004 100644
> +++ b/include/uapi/rdma/qedr-abi.h
> @@ -49,6 +49,7 @@ struct qedr_alloc_ucontext_resp {
> __u32 sges_per_recv_wr;
> __u32 sges_per_srq_wr;
> __u32 max_cqes;
> + __u8 dpm_enabled;
> };
Um, how is uapi compatibility achieved here? I don't see any size
tests related to qedr_alloc_ucontext_resp:
struct ib_ucontext *qedr_alloc_ucontext(struct ib_device *ibdev,
struct ib_udata *udata)
{
struct qedr_alloc_ucontext_resp uresp;
rc = ib_copy_to_udata(udata, &uresp, sizeof(uresp));
Seems bad.
Same with the other patch.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-19 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 13:01 [PATCH for-next 0/2] RDMA/qedr: Add feature indications to user-space Ram Amrani
[not found] ` <1497790871-23945-1-git-send-email-Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-06-18 13:01 ` [PATCH for-next 1/2] RDMA/qedr: Notify user application if DPM is supported Ram Amrani
[not found] ` <1497790871-23945-2-git-send-email-Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-06-19 15:55 ` Jason Gunthorpe [this message]
[not found] ` <20170619155553.GB10188-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-20 8:34 ` Amrani, Ram
[not found] ` <BN3PR07MB2578EC6DD9C3DF920388418AF8C50-EldUQEzkDQfpW3VS/XPqkOFPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-06-20 10:41 ` Leon Romanovsky
[not found] ` <20170620104104.GS17846-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-06-20 15:39 ` Jason Gunthorpe
[not found] ` <20170620153928.GB29283-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-22 11:27 ` Amrani, Ram
2017-06-22 11:27 ` Amrani, Ram
[not found] ` <BN3PR07MB2578A8CADFE59008A967A6E0F8DB0-EldUQEzkDQfpW3VS/XPqkOFPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-06-22 15:58 ` Jason Gunthorpe
2017-06-18 13:01 ` [PATCH for-next 2/2] RDMA/qedr: Notify user application number of supported WIDs Ram Amrani
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=20170619155553.GB10188@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=Ariel.Elior-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
--cc=Michal.Kalderon-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
--cc=Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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