From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Marian Barbu <barbu.d.m@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] FDIR issues when upgrading custom application from dpdk 1.8 to dpdk 2.0
Date: Wed, 08 Jul 2015 18:39:22 +0200 [thread overview]
Message-ID: <718191943.GArJdUoPBA@xps13> (raw)
In-Reply-To: <CANApEYtkPOckG=KAzP=GrjgApLQ3vPd7LqAOLbPows7GM_o6bw@mail.gmail.com>
2015-07-08 16:17, Marian Barbu:
> Hello,
>
> I've been working on upgrading a custom dpdk application from dpdk 1.8.0 to
> dpdk 2.0.0.
>
> I want to use FDIR to distribute the traffic based on IP to multiple
> queues, but I seem to get -95 (ENOTSUP) error code from
> *rte_eth_dev_fdir_set_masks.
> *I mention that this was all working fine with dpdk 1.8.0. Any ideas?
We had some troubles when migrating FDIR to a new API.
In DPDK 2.0, the old API you are using is implemented only for enic.
In order to use FDIR for ixgbe, you have to check the new API:
http://dpdk.org/doc/api-2.0/structrte__eth__fdir__filter.html
prev parent reply other threads:[~2015-07-08 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 16:17 Marian Barbu
2015-07-08 16:39 ` Thomas Monjalon [this message]
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=718191943.GArJdUoPBA@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=barbu.d.m@gmail.com \
--cc=dev@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).