DPDK usage discussions
 help / color / mirror / Atom feed
From: Jeremias Blendin <jeremias@blendin.org>
To: Paul Emmerich <emmericp@net.in.tum.de>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] FDir flex filters on XL710/i40e NICs with the new filter API
Date: Mon, 18 Jul 2016 18:36:43 +0200	[thread overview]
Message-ID: <CAFZrTr7R3pTZ3bBAsvB91pqiVU_p=KrnrdFHKUQ_i3zkuF3x3Q@mail.gmail.com> (raw)
In-Reply-To: <57739782.60708@net.in.tum.de>

Hi,

I am really curious about this issue as well. Any hint is appreciated.

Thanks!

2016-06-29 11:40 GMT+02:00 Paul Emmerich <emmericp@net.in.tum.de>:
> Hi,
>
> we are trying to use flex filters to match on payload bytes and our code
> stopped working with the new Filter API after upgrading to DPDK 2.2 or later
> (currently using 16.04).
>
> We use these filters to match on the bytes 42 and 43 of the payload, the
> filter worked with DPDK 2.0 with both XL710 and 82599 NICs with the old fdir
> filter API.
>
> We then upgraded to DPDK 2.2 and later to DPDK 16.04 and migrated to the new
> filter API. The filter still works on 82599 NICs but not on XL710 NICs.
>
> Any ideas what we might be doing wrong here?
>
> The initialization code can be found here:
> https://github.com/emmericp/MoonGen/blob/master/src/device.c#L115-L157
>
> Adding the filter is done here:
> https://github.com/emmericp/MoonGen/blob/master/lua/include/filter.lua#L356-L385
>
> rte_eth_dev_filter_ctrl() does not return an error and the same code works
> for the 82599 NIC. Yet, the filter matches no packets on XL710 NICs.
>
> Is there a minimal example for the flex filters somewhere that could help me
> track down this?
>
> Any help would be appreciated.
>
> Thanks!
>
>
>  Paul

  reply	other threads:[~2016-07-18 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  9:40 Paul Emmerich
2016-07-18 16:36 ` Jeremias Blendin [this message]
2016-08-19 16:39 ` Paul Emmerich

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='CAFZrTr7R3pTZ3bBAsvB91pqiVU_p=KrnrdFHKUQ_i3zkuF3x3Q@mail.gmail.com' \
    --to=jeremias@blendin.org \
    --cc=emmericp@net.in.tum.de \
    --cc=users@dpdk.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).