From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: Ingo Molnar <mingo@elte.hu>
Cc: Zach Brown <zach.brown@oracle.com>,
Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH] mthca: initialize send and receive queue locks separately
Date: Tue, 4 Jul 2006 12:42:19 +0300 [thread overview]
Message-ID: <20060704094219.GO21049@mellanox.co.il> (raw)
In-Reply-To: <20060704085653.GA13426@elte.hu>
Quoting r. Ingo Molnar <mingo@elte.hu>:
> Subject: Re: [PATCH] mthca: initialize send and receive queue locks separately
>
>
> * Michael S. Tsirkin <mst@mellanox.co.il> wrote:
>
> > > Initializing the locks separately in mthca_alloc_qp_common() stops the warning
> > > and will let lockdep enforce proper ordering on paths that acquire both locks.
> > >
> > > Signed-off-by: Zach Brown <zach.brown@oracle.com>
> >
> > This moves code out of a common function and so results in code
> > duplication and has memory cost.
>
> the patch below does the same via the lockdep_set_class() method, which
> has no cost on non-lockdep kernels.
>
> Ingo
>
> ---------------->
> Subject: lockdep: annotate drivers/infiniband/hw/mthca/mthca_qp.c
> From: Ingo Molnar <mingo@elte.hu>
>
> annotate mthca queue locks: split them into send and receive locks.
>
> (both can be held at once, but there is ordering between them which
> lockdep enforces)
I find this capability of lockdep very useful.
> Has no effect on non-lockdep kernels.
Hmm ... adding parameters to function still has text cost, I think. No?
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> drivers/infiniband/hw/mthca/mthca_qp.c | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
>
> Index: linux/drivers/infiniband/hw/mthca/mthca_qp.c
> ===================================================================
> --- linux.orig/drivers/infiniband/hw/mthca/mthca_qp.c
> +++ linux/drivers/infiniband/hw/mthca/mthca_qp.c
> @@ -222,9 +222,15 @@ static void *get_send_wqe(struct mthca_q
> (PAGE_SIZE - 1));
> }
>
> -static void mthca_wq_init(struct mthca_wq *wq)
> +/*
> + * Send and receive queues for two different lock classes:
> + */
> +static struct lock_class_key mthca_wq_send_lock_class, mthca_wq_recv_lock_class;
> +
Does this still have a small cost in data size on non-lockdep kernels, as well?
If yes, maybe some typedef/macro magic can be used to put this struct in an
unused elf section for such kernels?
> +static void mthca_wq_init(struct mthca_wq *wq, struct lock_class_key *key)
> {
> spin_lock_init(&wq->lock);
> + lockdep_set_class(&wq->lock, key);
> wq->next_ind = 0;
> wq->last_comp = wq->max - 1;
> wq->head = 0;
> @@ -845,10 +851,10 @@ int mthca_modify_qp(struct ib_qp *ibqp,
> mthca_cq_clean(dev, to_mcq(qp->ibqp.recv_cq), qp->qpn,
> qp->ibqp.srq ? to_msrq(qp->ibqp.srq) : NULL);
>
> - mthca_wq_init(&qp->sq);
> + mthca_wq_init(&qp->sq, &mthca_wq_send_lock_class);
> qp->sq.last = get_send_wqe(qp, qp->sq.max - 1);
>
> - mthca_wq_init(&qp->rq);
> + mthca_wq_init(&qp->rq, &mthca_wq_recv_lock_class);
> qp->rq.last = get_recv_wqe(qp, qp->rq.max - 1);
>
> if (mthca_is_memfree(dev)) {
> @@ -1112,8 +1118,8 @@ static int mthca_alloc_qp_common(struct
> qp->atomic_rd_en = 0;
> qp->resp_depth = 0;
> qp->sq_policy = send_policy;
> - mthca_wq_init(&qp->sq);
> - mthca_wq_init(&qp->rq);
> + mthca_wq_init(&qp->sq, &mthca_wq_send_lock_class);
> + mthca_wq_init(&qp->rq, &mthca_wq_recv_lock_class);
>
> ret = mthca_map_memfree(dev, qp);
> if (ret)
>
>
I'm pretty sure this still adds to code footprint due to extra function
parameters even on non-lockdep kernels. Will the following work?
@@ -1112,8 +1118,8 @@ static int mthca_alloc_qp_common(struct
qp->atomic_rd_en = 0;
qp->resp_depth = 0;
qp->sq_policy = send_policy;
mthca_wq_init(&qp->sq);
+ lockdep_set_class(&qp->sq.lock, &mthca_wq_send_lock_class);
mthca_wq_init(&qp->rq);
+ lockdep_set_class(&qp->rq.lock, &mthca_wq_recv_lock_class);
--
MST
next prev parent reply other threads:[~2006-07-04 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 22:50 Zach Brown
2006-07-04 7:03 ` Michael S. Tsirkin
2006-07-04 8:56 ` Ingo Molnar
2006-07-04 9:42 ` Michael S. Tsirkin [this message]
2006-07-04 11:56 ` Ingo Molnar
2006-07-04 12:52 ` Michael S. Tsirkin
2006-07-26 6:26 ` [PATCH] lockdep: don't pull in includes when lockdep disabled Michael S. Tsirkin
2006-07-26 6:33 ` Arjan van de Ven
2006-07-26 6:43 ` Michael S. Tsirkin
2006-07-26 7:13 ` Alexey Dobriyan
2006-07-04 16:38 ` [openib-general] [PATCH] mthca: initialize send and receive queue locks separately Zach Brown
2006-07-04 16:52 ` Michael S. Tsirkin
2006-07-04 20:39 ` Roland Dreier
2006-07-05 3:07 ` Michael S. Tsirkin
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=20060704094219.GO21049@mellanox.co.il \
--to=mst@mellanox.co.il \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=openib-general@openib.org \
--cc=zach.brown@oracle.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
all inboxes | Powered by JetHome®