From: Yann Droneaud <ydroneaud@opteya.com>
To: Hariprasad Shenai <hariprasad@chelsio.com>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
davem@davemloft.net, roland@purestorage.com,
swise@opengridcomputing.com, leedom@chelsio.com,
nirranjan@chelsio.com, kumaras@chelsio.com
Subject: Re: [PATCH 1/4] iw_cxgb4: Detect Ing. Padding Boundary at run-time
Date: Sun, 13 Jul 2014 13:48:39 +0200 [thread overview]
Message-ID: <1405252119.32637.16.camel@localhost.localdomain> (raw)
In-Reply-To: <1405091662-5270-2-git-send-email-hariprasad@chelsio.com>
Hi,
Le vendredi 11 juillet 2014 à 20:44 +0530, Hariprasad Shenai a écrit :
> Updates iw_cxgb4 to determine the Ingress Padding Boundary from
> cxgb4_lld_info, and take subsequent actions.
>
> Signed-off-by: Steve Wise <swise@opengridcomputing.com>
> Signed-off-by: Hariprasad Shenai <hariprasad@chelsio.com>
> ---
> drivers/infiniband/hw/cxgb4/cq.c | 4 ++--
> drivers/infiniband/hw/cxgb4/device.c | 21 +++++++++++++++++++++
> drivers/infiniband/hw/cxgb4/iw_cxgb4.h | 12 ++++++++++++
> drivers/infiniband/hw/cxgb4/provider.c | 4 ++--
> drivers/infiniband/hw/cxgb4/qp.c | 10 ++++++----
> drivers/infiniband/hw/cxgb4/t4.h | 8 --------
> drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c | 2 ++
> drivers/net/ethernet/chelsio/cxgb4/cxgb4_uld.h | 2 ++
> 8 files changed, 47 insertions(+), 16 deletions(-)
>
[...]
> diff --git a/drivers/infiniband/hw/cxgb4/device.c b/drivers/infiniband/hw/cxgb4/device.c
> index dd93aad..95e6c6c 100644
> --- a/drivers/infiniband/hw/cxgb4/device.c
> +++ b/drivers/infiniband/hw/cxgb4/device.c
> @@ -768,6 +768,27 @@ static struct c4iw_dev *c4iw_alloc(const struct cxgb4_lld_info *infop)
> }
> devp->rdev.lldi = *infop;
>
> + /* init various hw-queue params based on lld info */
> + pr_info("%s: ing. padding boundary is %d, egrsstatuspagesize = %d\n",
> + __func__, devp->rdev.lldi.sge_ingpadboundary,
> + devp->rdev.lldi.sge_egrstatuspagesize);
Is this really needed ?
Use dev_info() or perhaps dev_dbg() instead of pr_info().
Regards.
--
Yann Droneaud
OPTEYA
next prev parent reply other threads:[~2014-07-13 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 15:14 [PATCH 0/4] Misc. fixes for iw_cxgb4 Hariprasad Shenai
[not found] ` <1405091662-5270-1-git-send-email-hariprasad-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2014-07-11 15:14 ` [PATCH 1/4] iw_cxgb4: Detect Ing. Padding Boundary at run-time Hariprasad Shenai
2014-07-13 11:48 ` Yann Droneaud [this message]
2014-07-11 15:14 ` [PATCH 4/4] cxgb4/iw_cxgb4: work request logging feature Hariprasad Shenai
2014-07-11 15:14 ` [PATCH 2/4] cxgb4/iw_cxgb4: use firmware ord/ird resource limits Hariprasad Shenai
[not found] ` <1405091662-5270-3-git-send-email-hariprasad-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2014-07-13 11:59 ` Yann Droneaud
2014-07-11 15:14 ` [PATCH 3/4] cxgb4/iw_cxgb4: display TPTE on errors Hariprasad Shenai
[not found] ` <1405091662-5270-4-git-send-email-hariprasad-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2014-07-13 12:36 ` Yann Droneaud
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=1405252119.32637.16.camel@localhost.localdomain \
--to=ydroneaud@opteya.com \
--cc=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=kumaras@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=roland@purestorage.com \
--cc=swise@opengridcomputing.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).