DPDK patches and discussions
 help / color / mirror / Atom feed
From: Navneet Rao <navneet.rao@oracle.com>
To: Jan Fruhbauer <fruhbauer@invea.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] testpmd - configuration of the fdir filter
Date: Fri, 11 Sep 2015 11:45:22 -0700 (PDT)	[thread overview]
Message-ID: <7050d5b8-8044-4ca3-babd-8513bd3f881a@default> (raw)
In-Reply-To: <b91e0786-1c22-45b9-8035-e3b8e0d8cdf1@default>

I'm getting a fdir filter programming error after I do this --

 

 

./testpmd -c ffffffff -n 4 -- -i --pkt-filter-mode=perfect --rxq=2 --txq=2 --portmask=0x3 --nb-ports=2 --disable-rss

 

   testpmd> port stop all

   testpmd> flow_director_mask 0 vlan 0xefff src_mask 255.255.255.255 FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF 0xFFFF dst_mask 255.255.255.255 FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF 0xFFFF

   testpmd> flow_director_filter 0 add flow ipv4-udp src 192.168.10.100 dst 192.168.10.101 vlan 0x1 flexbytes (0x00,0x00) fwd queue 1 fd_id 1

   PMD: fdir_write_perfect_filter_82599(): Rx Queue=1 hash=10529

   PMD: fdir_write_perfect_filter_82599(): Timeout writing flow director filter.

   PMD: ixgbe_add_del_fdir_filter(): Fail to add FDIR filter!

   flow director programming error: (Connection timed out)

 

 

Any ideas? Debug?

 

Thanks

-Navneet

 

 

 

 

-----Original Message-----
From: Navneet Rao 
Sent: Wednesday, September 09, 2015 10:26 AM
To: Jan Fruhbauer
Subject: RE: [dpdk-dev] testpmd - configuration of the fdir filter

 

Hello Jan:

 

Please let me know if you were able to figure this out...

I am also running into similar issues!!!

 

Thanks

-Navneet

 

 

-----Original Message-----

From: Jan Fruhbauer [mailto:fruhbauer@invea.com] 

Sent: Friday, September 04, 2015 3:46 AM

To: HYPERLINK "mailto:dev@dpdk.org"dev@dpdk.org

Subject: [dpdk-dev] testpmd - configuration of the fdir filter

 

Hi,

 

I want to use the fdir filtering on a NIC based on the Intel 82599. I have tested the testpmd application. I configured masks and added a filter but the fdir filter never matched any packet. I even tried different masks and filters (with/without ports, TCP/UDP flow, IP prefixes, ...), but it never worked. Here is an example of commands I used during testing:

 

./testpmd -c 0xff -n 2 -- -i --rxq=2 --txq=2 --pkt-filter-mode=perfect

--portmask=0x3 --nb-ports=2 --disable-rss

testpmd> port stop 0

testpmd> flow_director_mask 0 vlan 0x0000 src_mask 255.255.255.255

FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF 0xFFFF dst_mask 255.255.255.255 FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF 0xFFFF

testpmd> flow_director_flex_mask 0 flow all

(0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0)

testpmd> port start 0

testpmd> flow_director_filter 0 add flow ipv4-tcp src 1.0.0.1 1 dst

2.0.0.1 1 vlan 0x0 flexbytes (0x00,0x00) fwd queue 1 fd_id 1

testpmd> start

 

Then I sent generated traffic (simple packets with ethernet/IP/TCP

headers) with parametrs I specified in the flow_director_filter to the NIC port 0 and all packets arrived to the queue 0.

 

Please, could you advise me what I am doing wrong? Maybe some other configuration I didn't notice?

 

Regards,

Jan

 

      parent reply	other threads:[~2015-09-11 18:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 10:45 Jan Fruhbauer
     [not found] ` <b91e0786-1c22-45b9-8035-e3b8e0d8cdf1@default>
2015-09-11 18:45   ` Navneet Rao [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=7050d5b8-8044-4ca3-babd-8513bd3f881a@default \
    --to=navneet.rao@oracle.com \
    --cc=dev@dpdk.org \
    --cc=fruhbauer@invea.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).