[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY1PR0701MB201215C9F38E8760732B595088A50@CY1PR0701MB2012.namprd07.prod.outlook.com>
Date: Tue, 3 Apr 2018 07:42:28 +0000
From: "Kalderon, Michal" <Michal.Kalderon@...ium.com>
To: Sinan Kaya <okaya@...eaurora.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"timur@...eaurora.org" <timur@...eaurora.org>,
"sulrich@...eaurora.org" <sulrich@...eaurora.org>
CC: "linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"Elior, Ariel" <Ariel.Elior@...ium.com>,
Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...pe.ca>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Elior, Ariel" <Ariel.Elior@...ium.com>
Subject: RE: [PATCH v5 3/3] RDMA/qedr: eliminate duplicate barriers on
weakly-ordered archs #2
> From: Sinan Kaya [mailto:okaya@...eaurora.org]
> Sent: Tuesday, April 03, 2018 5:30 AM
> To: linux-rdma@...r.kernel.org; timur@...eaurora.org;
> sulrich@...eaurora.org
> Cc: linux-arm-msm@...r.kernel.org; linux-arm-kernel@...ts.infradead.org;
> Kalderon, Michal <Michal.Kalderon@...ium.com>; Elior, Ariel
> <Ariel.Elior@...ium.com>; Doug Ledford <dledford@...hat.com>; Jason
> Gunthorpe <jgg@...pe.ca>; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH v5 3/3] RDMA/qedr: eliminate duplicate barriers on
> weakly-ordered archs #2
>
> On 3/22/2018 12:26 PM, Sinan Kaya wrote:
> > @@ -860,7 +860,7 @@ static void doorbell_cq(struct qedr_cq *cq, u32
> cons, u8 flags)
> > wmb();
> > cq->db.data.agg_flags = flags;
> > cq->db.data.value = cpu_to_le32(cons);
> > - writeq(cq->db.raw, cq->db_addr);
> > + writeq_relaxed(cq->db.raw, cq->db_addr);
>
> Given the direction to get rid of wmb() in front of writeX() functions, I have
> been reviewing this code. Under normal circumstances, I can get rid of all
> wmb() as follows.
>
> However, I started having my doubts now. Are these wmb() used as a SMP
> barrier too?
> I can't find any smp_Xmb() in drivers/infiniband/hw/qedr directory.
Your doubts are in place. You initial patch series modified writel to writel_relaxed
Simply removing the wmb is dangerous. The wmb before writel are used to make sure the
HW observes the changes in memory before we trigger the doorbell. Smp barriers here
wouldn't suffice, as on a single processor. we still need to make sure memory is updated
and not remained in cache when HW accesses it.
Reviewing the qedr barriers, I can find places where this may have not been necessary,
But definitely you can't simply remove this wmb barriers.
>
> static void doorbell_cq(struct qedr_cq *cq, u32 cons, u8 flags) {
> - /* Flush data before signalling doorbell */
> - wmb();
> cq->db.data.agg_flags = flags;
> cq->db.data.value = cpu_to_le32(cons);
> writeq(cq->db.raw, cq->db_addr); @@ -1870,8 +1868,7 @@ static int
> qedr_update_qp_state(struct qedr_dev *dev,
> */
>
> if (rdma_protocol_roce(&dev->ibdev, 1)) {
> - wmb();
> - writel_relaxed(qp->rq.db_data.raw, qp->rq.db);
> + writel(qp->rq.db_data.raw, qp->rq.db);
> /* Make sure write takes effect */
> mmiowb();
> }
> @@ -3275,8 +3272,7 @@ int qedr_post_send(struct ib_qp *ibqp, struct
> ib_send_wr *wr,
> * unchanged). For performance reasons we avoid checking for this
> * redundant doorbell.
> */
> - wmb();
> - writel_relaxed(qp->sq.db_data.raw, qp->sq.db);
> + writel(qp->sq.db_data.raw, qp->sq.db);
>
> /* Make sure write sticks */
> mmiowb();
> @@ -3362,9 +3358,6 @@ int qedr_post_recv(struct ib_qp *ibqp, struct
> ib_recv_wr *wr,
>
> qedr_inc_sw_prod(&qp->rq);
>
> - /* Flush all the writes before signalling doorbell */
> - wmb();
>
>
>
>
>
> --
> Sinan Kaya
> Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
> Technologies, Inc.
> Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux
> Foundation Collaborative Project.
Powered by blists - more mailing lists