From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: "Legacy, Allain" <Allain.Legacy@windriver.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 10:34:53 +0200 [thread overview]
Message-ID: <20170331083453.GX16796@autoinstall.dev.6wind.com> (raw)
In-Reply-To: <70A7408C6E1BFB41B192A929744D8523968FCD16@ALA-MBC.corp.ad.wrs.com>
On Thu, Mar 30, 2017 at 04:53:47PM +0000, Legacy, Allain wrote:
> > -----Original Message-----
> > From: Nélio Laranjeiro [mailto:nelio.laranjeiro@6wind.com]
> > Sent: Thursday, March 30, 2017 9:03 AM
> <...>
> > I found an issue on the id retrieval while receiving an high rate of the
> > same flow [1]. You may face the same issue. Can you verify with the
> > patch?
> >
> > Thanks,
> >
> > [1] http://dpdk.org/dev/patchwork/patch/22897/
>
> I had some difficulty applying that patch onto v17.02 so I took all of
> the patches to the mlx5 driver that are in dpdk-next-net just to be
> sure I had all other outstanding fixes.
>
> The behavior did not change. I still see flows that are not marked
> even after a flow rule has been created to match on that particular
> flow. It seems like it works in batches... 10-20 flows will work,
> and then the next 10-20 flows won't work, and then the next 10-20
> flows will work. But, in all cases I have logs that show that the
> flow rules were created properly for all flows, and destroyed properly
> at the end of each test. It seems pretty consistent that the first
> test after a NIC reset always works on all flows, but then subsequent
> tests see variable results. Every so often I get another test run
> that has no issues but then the failure pattern resumes on the next
> attemp.
+ 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.
Thanks,
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2017-03-31 8:35 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 [this message]
2017-03-31 13:16 ` Legacy, Allain
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=20170331083453.GX16796@autoinstall.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=Allain.Legacy@windriver.com \
--cc=Matt.Peters@windriver.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--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).