netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Gal Pressman <galpress@amazon.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH iproute2-next] rdma: Add driver QP type string
Date: Mon, 5 Aug 2019 13:08:02 -0600	[thread overview]
Message-ID: <fd623a4e-d076-3eea-2d1e-7702812b0dfc@gmail.com> (raw)
In-Reply-To: <20190804080756.58364-1-galpress@amazon.com>

On 8/4/19 2:07 AM, Gal Pressman wrote:
> RDMA resource tracker now tracks driver QPs as well, add driver QP type
> string to qp_types_to_str function.

"now" means which kernel release? Leon: should this be in master or -next?

> 
> Signed-off-by: Gal Pressman <galpress@amazon.com>
> ---
>  rdma/res.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/rdma/res.c b/rdma/res.c
> index ef863f142eca..97a7b9640185 100644
> --- a/rdma/res.c
> +++ b/rdma/res.c
> @@ -148,9 +148,11 @@ const char *qp_types_to_str(uint8_t idx)
>  						     "UC", "UD", "RAW_IPV6",
>  						     "RAW_ETHERTYPE",
>  						     "UNKNOWN", "RAW_PACKET",
> -						     "XRC_INI", "XRC_TGT" };
> +						     "XRC_INI", "XRC_TGT",
> +						     [0xFF] = "DRIVER",
> +	};
>  
> -	if (idx < ARRAY_SIZE(qp_types_str))
> +	if (idx < ARRAY_SIZE(qp_types_str) && qp_types_str[idx])
>  		return qp_types_str[idx];
>  	return "UNKNOWN";
>  }
> 


  parent reply	other threads:[~2019-08-05 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04  8:07 [PATCH iproute2-next] rdma: Add driver QP type string Gal Pressman
2019-08-04  9:52 ` Leon Romanovsky
2019-08-05 19:08 ` David Ahern [this message]
2019-08-06  6:41   ` Gal Pressman
2019-08-06  6:54     ` Leon Romanovsky
2019-08-07 19:07 ` David Ahern

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=fd623a4e-d076-3eea-2d1e-7702812b0dfc@gmail.com \
    --to=dsahern@gmail.com \
    --cc=galpress@amazon.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).