DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Sujith Sankar (ssujith)" <ssujith@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Query on the use of FDIR feature
Date: Wed, 23 Apr 2014 07:07:27 +0000	[thread overview]
Message-ID: <CF7D6493.172D4%ssujith@cisco.com> (raw)

Hi,

Could someone kindly give information about the following aspects of the use of FDIR?  It is about adding of flow classification rule using fdir_add_perfect_filter()

1.  For SCTP, what are the mandatory fields to be provided in struct rte_fdir_filter ?  Is it enough if protocol  and src and dst IP addresses are provided?
2.  If vlan id is specified in struct rte_fdir_filter,  what other fields are mandatory?
3.  In the case of IPV6, is it enough if protocol, src and dst IPV6 addresses and src and dst L4 port numbers are provided?
4.  Is it mandatory that the applications have to provide protocol, src and dst IPV4 addresses and port numbers when it is trying to add filter for IPV4?

The programmers guide does not clarify these, and hence the email to the group.

Thanks in advance,
-Sujith

                 reply	other threads:[~2014-04-23  7:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CF7D6493.172D4%ssujith@cisco.com \
    --to=ssujith@cisco.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).