gt; >
> > Subject: Re: [dpdk-dev] [PATCH] ethdev: add roughly match pattern
> >
> > On Tue, May 30, 2017 at 02:46:30PM +0200, Adrien Mazarguil wrote:
> > >Hi Zhang,
> > >
> > >You should cram "flow API" somewhere in the title of such commit
> -Original Message-
> From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
> Sent: Wednesday, May 31, 2017 3:52 PM
> To: Zhang, Qi Z ; dev@dpdk.org
> Cc: Adrien Mazarguil ; Mcnamara, John
>
> Subject: Re: [dpdk-dev] [PATCH] ethdev: add roughly match pattern
>
&
On Tue, May 30, 2017 at 02:46:30PM +0200, Adrien Mazarguil wrote:
Hi Zhang,
You should cram "flow API" somewhere in the title of such commits.
On Tue, May 23, 2017 at 07:28:54PM -0400, Qi Zhang wrote:
Add new meta pattern item RTE_FLOW_TYPE_ITEM_ROUGHLY.
This is for device that support no-per
Hi Zhang,
You should cram "flow API" somewhere in the title of such commits.
On Tue, May 23, 2017 at 07:28:54PM -0400, Qi Zhang wrote:
> Add new meta pattern item RTE_FLOW_TYPE_ITEM_ROUGHLY.
>
> This is for device that support no-perfect match option.
> Usually a no-perfect match is fast but the
Add new meta pattern item RTE_FLOW_TYPE_ITEM_ROUGHLY.
This is for device that support no-perfect match option.
Usually a no-perfect match is fast but the cost is accuracy.
i.e. Signature Match only match pattern's hash value, but it is
possible two different patterns have the same hash value.
Mat
5 matches
Mail list logo