All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Barbette <barbette@kth.se>
To: Georgios Katsikas <katsikas.gp@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
	"adrien.mazarguil@6wind.com" <adrien.mazarguil@6wind.com>
Subject: Re: Flow Director vs. 5-tuple filters on a 10GbE Intel 82599 ES NIC
Date: Wed, 16 Jan 2019 09:55:44 +0100	[thread overview]
Message-ID: <c6c13c61-5b9a-4a33-0b5e-863e19bd2771@kth.se> (raw)
In-Reply-To: <1544538698808.34010@kth.se>

Hi Georgios,

I looked at the documentation written in C...

ixgbe will first parse the rule as a 5-tuple filter. If parsing works, 
then it will install it as a 5-tuple filter. Then it will try ethertype 
filters, then syn filters, and if any of those "specific" filters did 
not work, then it will use fdir.

As far as I see, there is no way to prevent using 5-tuple/ntuple filters 
if the filter can match.

So currently one is limited to 128 5-tuple flows, while actually 8K 
could be used... Maybe a flag could be added to select the underlying 
hardware, but given ixgbe is getting old and the lack of answer, I doubt 
Intel will help on this...

Tom

PS: If some fields are missing (eg. no dst port), then it seems the 
ntuple will not be used and the parsing will continue. Maybe that can be 
used as a trick ? But it leads to potential collisions...




On 2018-12-11 15:31, Tom Barbette wrote:
> ?CC-ing maintainers.
> 
> 
> ________________________________
> De : Georgios Katsikas <katsikas.gp@gmail.com>
> Envoyé : mardi 4 décembre 2018 11:41
> À : dev@dpdk.org
> Cc : Tom Barbette
> Objet : Flow Director vs. 5-tuple filters on a 10GbE Intel 82599 ES NIC
> 
> Dear all,
> 
> I am performing rule installation/deletion benchmarks on a dual port 10 GbE Intel 82599 ES NIC using DPDK 18.11.
> The benchmark installs increasing number of rules (5 to 8000), measures the rule installation rate and latency and then deletes the rules (measuring again the rule deletion rate/latency).
> The rule sets comprise of rules with exact matches (no masks involved) as follows:
> 
> Simple rule
> flow create 0 ingress pattern eth / ipv4 dst is 129.72.224.94 / end actions queue index 0 / end
> 
> More complicated rule
> flow create 0 ingress pattern eth / ipv4 dst is 46.54.254.68 src is 49.75.141.195 proto is 17 / udp dst is 26561 src is 7242 / end actions queue index 0 / end
> 
> No matter how simple or complicated the rules are, I am not able to install more than 128 rules on this NIC.
> 
> Here comes my question
> 
> According to the specification<https://www.intel.com/content/www/us/en/embedded/products/networking/82599-10-gbe-controller-datasheet.html>, this NIC can accommodate up to 128 5-tuple filters, which very well agrees with my observation above.
> However, the same document states that this NIC can also accommodate up to 8000 Flow Director filters.
> What is the practical difference between a 5-tuple and a Flow Director rule in this case? How can I exploit these 8k filters using DPDK 18.11?
> 
> Thanks in advance,
> Georgios
> 
> 
> 

      parent reply	other threads:[~2019-01-16  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 10:41 Flow Director vs. 5-tuple filters on a 10GbE Intel 82599 ES NIC Georgios Katsikas
2018-12-07  6:38 ` Georgios Katsikas
2018-12-11 14:31 ` Tom Barbette
2018-12-18 10:11   ` Georgios Katsikas
2019-01-16  8:55   ` Tom Barbette [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=c6c13c61-5b9a-4a33-0b5e-863e19bd2771@kth.se \
    --to=barbette@kth.se \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=katsikas.gp@gmail.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=wenzhuo.lu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.