[dpdk-dev] Changes to 5tuple IPv4 filters in dpdk v2.0

2015-08-05 Thread Vladimir Medvedkin
Hi Kam, Flow director can filter by src/dst prefix, but the src/dst prefix length is global for all rules. So, if you decide to specify /16 dst network, all rules will have /16 prefix length for dst address. Regards, Vladimir 2015-08-05 17:53 GMT+03:00 Kamraan Nasim : > Hi Vladimir, > > Thank y

[dpdk-dev] Changes to 5tuple IPv4 filters in dpdk v2.0

2015-08-05 Thread Kamraan Nasim
Hi Vladimir, Thank you for the link. Seems to simply be an abstraction over the existing filters so it is safe for me to upgrade to v2.0 :) Since we are on the subject, are you aware of any filters on 82599 or Fortville that may provide subnet filtering(I can specify something like 192.168.0.0/16

[dpdk-dev] Changes to 5tuple IPv4 filters in dpdk v2.0

2015-08-05 Thread Vladimir Medvedkin
Hi Kam, 1) The reason is discussed in http://dpdk.org/ml/archives/dev/2014-September/005179.html 2) No, it's still not supported (on current NICs). At the moment ntuple is supported only by igb and ixgbe. If you look at drivers/net/ixgbe/ixgbe_ethdev.c you can see ntuple_filter_to_5tuple function

[dpdk-dev] Changes to 5tuple IPv4 filters in dpdk v2.0

2015-08-04 Thread Kamraan Nasim
Hi DPDK community, I've been using DPDK v1.7 and v1.8 for the past year. On updating to v2.0.0, I see that *rte_5tuple_filter* has been deprecated as well as the associated install/remove call,* rte_eth_dev_add_5tuple_filter()* I now see that rte_eth_ntuple_filter has been added in place. 1) Is