From: Gal Pressman <galpress@amazon.com>
To: Shiraz Saleem <shiraz.saleem@intel.com>, <dledford@redhat.com>,
<jgg@ziepe.ca>, <davem@davemloft.net>
Cc: <linux-rdma@vger.kernel.org>, <netdev@vger.kernel.org>,
<mustafa.ismail@intel.com>, <jeffrey.t.kirsher@intel.com>
Subject: Re: [RFC v1 08/19] RDMA/irdma: Add privileged UDA queue implementation
Date: Sun, 24 Feb 2019 13:42:17 +0200 [thread overview]
Message-ID: <bb00f433-d699-7091-964b-50ebc487290f@amazon.com> (raw)
In-Reply-To: <20190215171107.6464-9-shiraz.saleem@intel.com>
On 15-Feb-19 19:10, Shiraz Saleem wrote:
> +/**
> + * irdma_puda_poll_info - poll cq for completion
> + * @cq: cq for poll
> + * @info: info return for successful completion
> + */
> +static enum irdma_status_code
> +irdma_puda_poll_info(struct irdma_sc_cq *cq, struct irdma_puda_cmpl_info *info)
> +{
> + struct irdma_cq_uk *cq_uk = &cq->cq_uk;
> + u64 qword0, qword2, qword3, qword6;
> + __le64 *cqe;
> + __le64 *ext_cqe = NULL;
> + u64 qword7 = 0;
> + u64 comp_ctx;
> + bool valid_bit;
> + bool ext_valid = 0;
> + u32 major_err, minor_err;
> + u32 peek_head;
> + bool error;
> + u8 polarity;
> +
> + cqe = IRDMA_GET_CURRENT_CQ_ELEM(&cq->cq_uk);
> + get_64bit_val(cqe, 24, &qword3);
> + valid_bit = (bool)RS_64(qword3, IRDMA_CQ_VALID);
> + if (valid_bit != cq_uk->polarity)
> + return IRDMA_ERR_Q_EMPTY;
> +
> + if (cq->dev->hw_attrs.hw_rev > IRDMA_GEN_1)
> + ext_valid = (bool)RS_64(qword3, IRDMA_CQ_EXTCQE);
> +
> + if (ext_valid) {
> + enum irdma_status_code ret = 0;
> +
> + peek_head = (cq_uk->cq_ring.head + 1) % cq_uk->cq_ring.size;
> + ext_cqe = cq_uk->cq_base[peek_head].buf;
> + get_64bit_val(ext_cqe, 24, &qword7);
> + polarity = (u8)RS_64(qword7, IRDMA_CQ_VALID);
> + if (!peek_head)
> + polarity ^= 1;
> + if (polarity != cq_uk->polarity)
> + return IRDMA_ERR_Q_EMPTY;
> +
> + IRDMA_RING_MOVE_HEAD(cq_uk->cq_ring, ret);
Should you check for 'ret' value here? It was initialized to 0 and overriden
here but I can't see any actual use for it.
> + if (IRDMA_RING_CURRENT_HEAD(cq_uk->cq_ring) == 0)
> + cq_uk->polarity = !cq_uk->polarity;
> + /* update cq tail in cq shadow memory also */
> + IRDMA_RING_MOVE_TAIL(cq_uk->cq_ring);
> + }
> +
> + irdma_debug_buf(cq->dev, IRDMA_DEBUG_PUDA, "PUDA CQE", cqe, 32);
> + if (ext_valid)
> + irdma_debug_buf(cq->dev, IRDMA_DEBUG_PUDA, "PUDA EXT-CQE",
> + ext_cqe, 32);
> +
> + error = (bool)RS_64(qword3, IRDMA_CQ_ERROR);
> + if (error) {
> + irdma_debug(cq->dev, IRDMA_DEBUG_PUDA, "receive error\n");
> + major_err = (u32)(RS_64(qword3, IRDMA_CQ_MAJERR));
> + minor_err = (u32)(RS_64(qword3, IRDMA_CQ_MINERR));
> + info->compl_error = major_err << 16 | minor_err;
> + return IRDMA_ERR_CQ_COMPL_ERROR;
> + }
> +
> + get_64bit_val(cqe, 0, &qword0);
> + get_64bit_val(cqe, 16, &qword2);
> +
> + info->q_type = (u8)RS_64(qword3, IRDMA_CQ_SQ);
> + info->qp_id = (u32)RS_64(qword2, IRDMACQ_QPID);
> + if (cq->dev->hw_attrs.hw_rev > IRDMA_GEN_1)
> + info->ipv4 = (bool)RS_64(qword3, IRDMACQ_IPV4);
> +
> + get_64bit_val(cqe, 8, &comp_ctx);
> + info->qp = (struct irdma_qp_uk *)(unsigned long)comp_ctx;
> + info->wqe_idx = (u32)RS_64(qword3, IRDMA_CQ_WQEIDX);
> +
> + if (info->q_type == IRDMA_CQE_QTYPE_RQ) {
> + if (ext_valid) {
> + info->vlan_valid = (bool)RS_64(qword7, IRDMA_CQ_UDVLANVALID);
> + if (info->vlan_valid) {
> + get_64bit_val(ext_cqe, 16, &qword6);
> + info->vlan = (u16)RS_64(qword6, IRDMA_CQ_UDVLAN);
> + }
> + info->smac_valid = (bool)RS_64(qword7, IRDMA_CQ_UDSMACVALID);
> + if (info->smac_valid) {
> + get_64bit_val(ext_cqe, 16, &qword6);
> + info->smac[0] = (u8)((qword6 >> 40) & 0xFF);
> + info->smac[1] = (u8)((qword6 >> 32) & 0xFF);
> + info->smac[2] = (u8)((qword6 >> 24) & 0xFF);
> + info->smac[3] = (u8)((qword6 >> 16) & 0xFF);
> + info->smac[4] = (u8)((qword6 >> 8) & 0xFF);
> + info->smac[5] = (u8)(qword6 & 0xFF);
> + }
> + }
> +
> + if (cq->dev->hw_attrs.hw_rev == IRDMA_GEN_1) {
> + info->vlan_valid = (bool)RS_64(qword3, IRDMA_VLAN_TAG_VALID);
> + info->l4proto = (u8)RS_64(qword2, IRDMA_UDA_L4PROTO);
> + info->l3proto = (u8)RS_64(qword2, IRDMA_UDA_L3PROTO);
> + }
> +
> + info->payload_len = (u32)RS_64(qword0, IRDMACQ_PAYLDLEN);
> + }
> +
> + return 0;
> +}
next prev parent reply other threads:[~2019-02-24 11:42 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 17:10 [RFC v1 00/19] Add unified Intel Ethernet RDMA driver (irdma) Shiraz Saleem
2019-02-15 17:10 ` [RFC v1 01/19] net/i40e: Add peer register/unregister to struct i40e_netdev_priv Shiraz Saleem
2019-02-15 17:22 ` Jason Gunthorpe
2019-02-21 2:19 ` Saleem, Shiraz
2019-02-21 19:35 ` Jason Gunthorpe
2019-02-22 20:13 ` Ertman, David M
2019-02-22 20:23 ` Jason Gunthorpe
2019-03-13 2:11 ` Jeff Kirsher
2019-03-13 13:28 ` Jason Gunthorpe
2019-05-10 13:31 ` Shiraz Saleem
2019-05-10 18:17 ` Jason Gunthorpe
2019-02-15 17:10 ` [RFC v1 02/19] net/ice: Create framework for VSI queue context Shiraz Saleem
2019-02-15 17:10 ` [RFC v1 03/19] net/ice: Add support for ice peer devices and drivers Shiraz Saleem
2019-02-15 17:10 ` [RFC v1 04/19] RDMA/irdma: Add driver framework definitions Shiraz Saleem
2019-02-24 15:02 ` Gal Pressman
2019-02-26 21:08 ` Saleem, Shiraz
2019-02-15 17:10 ` [RFC v1 05/19] RDMA/irdma: Implement device initialization definitions Shiraz Saleem
2019-02-15 17:10 ` [RFC v1 06/19] RDMA/irdma: Implement HW Admin Queue OPs Shiraz Saleem
2019-02-15 17:10 ` [RFC v1 07/19] RDMA/irdma: Add HMC backing store setup functions Shiraz Saleem
2019-02-15 17:10 ` [RFC v1 08/19] RDMA/irdma: Add privileged UDA queue implementation Shiraz Saleem
2019-02-24 11:42 ` Gal Pressman [this message]
2019-02-15 17:10 ` [RFC v1 09/19] RDMA/irdma: Add QoS definitions Shiraz Saleem
2019-02-15 17:10 ` [RFC v1 10/19] RDMA/irdma: Add connection manager Shiraz Saleem
2019-02-24 11:21 ` Gal Pressman
2019-02-25 18:46 ` Jason Gunthorpe
2019-02-26 21:07 ` Saleem, Shiraz
2019-02-15 17:10 ` [RFC v1 11/19] RDMA/irdma: Add PBLE resource manager Shiraz Saleem
2019-02-27 6:58 ` Leon Romanovsky
2019-02-15 17:10 ` [RFC v1 12/19] RDMA/irdma: Implement device supported verb APIs Shiraz Saleem
2019-02-15 17:35 ` Jason Gunthorpe
2019-02-15 22:19 ` Shiraz Saleem
2019-02-15 22:32 ` Jason Gunthorpe
2019-02-20 14:52 ` Saleem, Shiraz
2019-02-20 16:51 ` Jason Gunthorpe
2019-02-24 14:35 ` Gal Pressman
2019-02-25 18:50 ` Jason Gunthorpe
2019-02-26 21:09 ` Saleem, Shiraz
2019-02-26 21:09 ` Saleem, Shiraz
2019-02-27 7:31 ` Gal Pressman
2019-02-15 17:11 ` [RFC v1 13/19] RDMA/irdma: Add RoCEv2 UD OP support Shiraz Saleem
2019-02-27 6:50 ` Leon Romanovsky
2019-02-15 17:11 ` [RFC v1 14/19] RDMA/irdma: Add user/kernel shared libraries Shiraz Saleem
2019-02-15 17:11 ` [RFC v1 15/19] RDMA/irdma: Add miscellaneous utility definitions Shiraz Saleem
2019-02-15 17:47 ` Jason Gunthorpe
2019-02-20 7:51 ` Leon Romanovsky
2019-02-20 14:53 ` Saleem, Shiraz
2019-02-20 16:53 ` Jason Gunthorpe
2019-02-15 17:11 ` [RFC v1 16/19] RDMA/irdma: Add dynamic tracing for CM Shiraz Saleem
2019-02-15 17:11 ` [RFC v1 17/19] RDMA/irdma: Add ABI definitions Shiraz Saleem
2019-02-15 17:16 ` Jason Gunthorpe
2019-02-20 14:52 ` Saleem, Shiraz
2019-02-20 16:50 ` Jason Gunthorpe
2019-02-15 17:11 ` [RFC v1 18/19] RDMA/irdma: Add Kconfig and Makefile Shiraz Saleem
2019-02-15 17:11 ` [RFC v1 19/19] RDMA/irdma: Update MAINTAINERS file Shiraz Saleem
2019-02-15 17:20 ` [RFC v1 00/19] Add unified Intel Ethernet RDMA driver (irdma) 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=bb00f433-d699-7091-964b-50ebc487290f@amazon.com \
--to=galpress@amazon.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shiraz.saleem@intel.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).