From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Bernard Metzler <bmt-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 10/14] SIWv2: Transmit path: siw_qp_tx.c
Date: Sat, 18 Jun 2011 19:47:29 +0200 [thread overview]
Message-ID: <BANLkTimSqwBK_pEGsydCAEvO=S6WVVzDPQ@mail.gmail.com> (raw)
In-Reply-To: <1308228153-22720-1-git-send-email-bmt-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org>
On Thu, Jun 16, 2011 at 2:42 PM, Bernard Metzler <bmt-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org> wrote:
> ---
> drivers/infiniband/hw/siw/siw_qp_tx.c | 1332 +++++++++++++++++++++++++++++++++
> 1 files changed, 1332 insertions(+), 0 deletions(-)
> create mode 100644 drivers/infiniband/hw/siw/siw_qp_tx.c
>
> diff --git a/drivers/infiniband/hw/siw/siw_qp_tx.c b/drivers/infiniband/hw/siw/siw_qp_tx.c
[ ... ]
> +/*
> + * Write out iov referencing hdr, data and trailer of current FPDU.
> + * Update transmit state dependent on write return status
> + */
> +static int siw_tx_hdt(struct siw_iwarp_tx *c_tx, struct socket *s)
> +{
> + struct siw_wqe *wqe = c_tx->wqe;
> + struct siw_sge *sge = &wqe->wr.sgl.sge[c_tx->sge_idx],
> + *first_sge = sge;
> + struct siw_mr *mr = NULL;
> + struct ib_umem_chunk *chunk = c_tx->umem_chunk;
> +
> + struct kvec iov[MAX_ARRAY];
> + struct page *page_array[MAX_ARRAY];
> + struct msghdr msg = {.msg_flags = MSG_DONTWAIT};
> +
> + int seg = 0, do_crc = c_tx->do_crc, is_kva = 0, rv;
> + unsigned int data_len = c_tx->bytes_unsent,
> + hdr_len = 0,
> + trl_len = 0,
> + sge_off = c_tx->sge_off,
> + sge_idx = c_tx->sge_idx,
> + pg_idx = c_tx->pg_idx;
Have you run the siw source code through sparse ? Sparse reports the
following for the above:
drivers/infiniband/hw/siw/siw_qp_tx.c:694:1: warning: the frame size
of 1120 bytes is larger than 1024 bytes
I assume that you know that one should be careful with stack
allocations in the kernel ?
> + if (tx_type == RDMAP_RDMA_READ_REQ) {
This is what the compiler says about the above statement:
drivers/infiniband/hw/siw/siw_qp_tx.c:1145:15: warning: comparison
between enum siw_wr_opcode and enum rdma_opcode
So how can that statement be correct ?
Bart.
--
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:[~2011-06-18 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 12:42 [PATCH 10/14] SIWv2: Transmit path: siw_qp_tx.c Bernard Metzler
[not found] ` <1308228153-22720-1-git-send-email-bmt-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org>
2011-06-18 17:47 ` Bart Van Assche [this message]
[not found] ` <BANLkTimSqwBK_pEGsydCAEvO=S6WVVzDPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-20 12:33 ` Bernard Metzler
[not found] ` <OF564FAAA3.FC8A4AB9-ONC12578B5.003C1E38-C12578B5.0044F0C1-Xeyd2O9EBijQT0dZR+AlfA@public.gmane.org>
2011-06-20 16:32 ` Bart Van Assche
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='BANLkTimSqwBK_pEGsydCAEvO=S6WVVzDPQ@mail.gmail.com' \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=bmt-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-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;
as well as URLs for NNTP newsgroup(s).