From: "Legacy, Allain" <Allain.Legacy@windriver.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Olga Shern" <olgas@mellanox.com>
Cc: "Adrien Mazarguil (adrien.mazarguil@6wind.com)"
<adrien.mazarguil@6wind.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Peters, Matt" <Matt.Peters@windriver.com>
Subject: Re: [dpdk-dev] mlx5 flow create/destroy behaviour
Date: Fri, 31 Mar 2017 13:16:51 +0000 [thread overview]
Message-ID: <70A7408C6E1BFB41B192A929744D8523968FE804@ALA-MBC.corp.ad.wrs.com> (raw)
In-Reply-To: <20170331083453.GX16796@autoinstall.dev.6wind.com>
> -----Original Message-----
> From: Nélio Laranjeiro [mailto:nelio.laranjeiro@6wind.com]
> Sent: Friday, March 31, 2017 4:35 AM
<...>
> + Olga Shern,
>
> Allain,
>
> Thanks for all this tests, for this last point is seems to be a firmware or
> hardware issue, I don't have any way to help on that case.
>
> I suggest you to contact directly Mellanox to have some support regarding
> this.
Ok, we will do that.
I was able to reproduce this using testpmd rather than our own application. If I sent you the commands (off list) that I used and steps to reproduce would you be willing to confirm that our exact setup works for you?
Regards,
Allain
next prev parent reply other threads:[~2017-03-31 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 12:42 Legacy, Allain
2017-03-28 15:36 ` Nélio Laranjeiro
2017-03-28 16:16 ` Legacy, Allain
2017-03-29 9:45 ` Nélio Laranjeiro
2017-03-29 12:29 ` Legacy, Allain
2017-03-30 13:03 ` Nélio Laranjeiro
2017-03-30 16:53 ` Legacy, Allain
2017-03-31 8:34 ` Nélio Laranjeiro
2017-03-31 13:16 ` Legacy, Allain [this message]
2017-03-31 13:34 ` Nélio Laranjeiro
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=70A7408C6E1BFB41B192A929744D8523968FE804@ALA-MBC.corp.ad.wrs.com \
--to=allain.legacy@windriver.com \
--cc=Matt.Peters@windriver.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=olgas@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).