DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: "Xueming(Steven) Li" <xuemingl@mellanox.com>
Cc: Nelio Laranjeiro <notifications@github.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: dump flow create error message
Date: Wed, 7 Feb 2018 07:50:00 +0100	[thread overview]
Message-ID: <20180207065000.ll4s4sw2rxcf23tg@laranjeiro-vm.dev.6wind.com> (raw)
In-Reply-To: <VI1PR05MB1678E843300D47E672D984DBACFD0@VI1PR05MB1678.eurprd05.prod.outlook.com>

On Tue, Feb 06, 2018 at 02:20:28PM +0000, Xueming(Steven) Li wrote:
> Hi Nelio,
> 
> > -----Original Message-----
> > From: Nélio Laranjeiro [mailto:nelio.laranjeiro@6wind.com]
> > Sent: Tuesday, February 6, 2018 9:22 PM
> > To: Xueming(Steven) Li <xuemingl@mellanox.com>
> > Cc: Nelio Laranjeiro <notifications@github.com>; dev@dpdk.org; Shahaf
> > Shuler <shahafs@mellanox.com>
> > Subject: Re: [dpdk-dev] [PATCH] net/mlx5: dump flow create error message
> > 
> > On Tue, Feb 06, 2018 at 08:52:53PM +0800, Xueming Li wrote:
> > > Add error message dump when flow create error happened.
> > >
> > > Signed-off-by: Xueming Li <xuemingl@mellanox.com>
> > > ---
> > >  drivers/net/mlx5/mlx5_flow.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/drivers/net/mlx5/mlx5_flow.c
> > > b/drivers/net/mlx5/mlx5_flow.c index e38452ef3..ea90556d0 100644
> > > --- a/drivers/net/mlx5/mlx5_flow.c
> > > +++ b/drivers/net/mlx5/mlx5_flow.c
> > > @@ -1890,6 +1890,7 @@ priv_flow_create(struct priv *priv,
> > >  	DEBUG("Flow created %p", (void *)flow);
> > >  	return flow;
> > >  exit:
> > > +	ERROR("Flow create error: %s", error->message);
> > >  	for (i = 0; i != hash_rxq_init_n; ++i) {
> > >  		if (parser.queue[i].ibv_attr)
> > >  			rte_free(parser.queue[i].ibv_attr);
> > > --
> > > 2.13.3
> > 
> > Hi Xueming,
> > 
> > Can you move this debug message to mlx5_flow_create().
> 
> This function also called by control flow and fdir functions, 
> here should be the best place.

Make sense,

Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>

Thanks,

-- 
Nélio Laranjeiro
6WIND

  reply	other threads:[~2018-02-07  6:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 12:52 Xueming Li
2018-02-06 13:22 ` Nélio Laranjeiro
2018-02-06 14:20   ` Xueming(Steven) Li
2018-02-07  6:50     ` Nélio Laranjeiro [this message]
2018-02-13 17:11       ` Thomas Monjalon

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=20180207065000.ll4s4sw2rxcf23tg@laranjeiro-vm.dev.6wind.com \
    --to=nelio.laranjeiro@6wind.com \
    --cc=dev@dpdk.org \
    --cc=notifications@github.com \
    --cc=shahafs@mellanox.com \
    --cc=xuemingl@mellanox.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).