DPDK usage discussions
 help / color / mirror / Atom feed
From: "Fu, Qiaobin" <qiaobinf@bu.edu>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Work with IP variable headers
Date: Tue, 4 Apr 2017 20:29:27 +0000	[thread overview]
Message-ID: <7C7AFFF4-92C8-4CE0-8515-A1B3E430C233@bu.edu> (raw)

Hi,

Currently, I am working on a module that classifies packets based on the L3/L4 headers, like the destination address, port number, etc. However, due to options, we need to deal with IP variable headers: e.g., the options for IPv4, and extension headers for IPv6.

For the ntuple filters, I found that they can direct packets with variable IPv4/IPv6 headers to the corresponding queues as specified by the filters.

However, after receiving the IP packets with variable headers from the NIC, we cannot use ACL rules to classify them. This is because only packets with fixed IPv4/ IPv6 header are supported by ACL rules in the current implementation. So, I am wondering does DPDK have some functions to help to deal with such packets?

Any suggestions are appreciated!

Best,
Qiaobin

                 reply	other threads:[~2017-04-04 20:29 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=7C7AFFF4-92C8-4CE0-8515-A1B3E430C233@bu.edu \
    --to=qiaobinf@bu.edu \
    --cc=users@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).