From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: dev@dpdk.org
Cc: Felix Marti <felix@chelsio.com>,
Kumar Sanghvi <kumaras@chelsio.com>,
Nirranjan Kirubaharan <nirranjan@chelsio.com>
Subject: [dpdk-dev] Query on Filtering Support in DPDK
Date: Mon, 30 Nov 2015 18:19:44 +0530 [thread overview]
Message-ID: <20151130124943.GA15383@scalar.blr.asicdesigners.com> (raw)
Hi,
We are working towards adding h/w based filtering support in cxgbe PMD.
Chelsio T5 supports carrying out filtering in hardware which supports 3
actions to carry out on a packet which hit a filter viz.
1. Action Pass - Packets hitting a filter rule can be directed to a
particular RXQ.
2. Action Drop - Packets hitting a filter rule are dropped in h/w.
3. Action Switch - Packets hitting a filter rule can be switched in h/w
from one port to another, without involvement of host. Also, the
action Switch also supports rewrite of src-mac/dst-mac headers as
well as rewrite of vlan headers. It also supports rewrite of IP
headers and thereby, supports NAT (Network Address Translation)
in h/w.
Also, each filter rule can optionally support specifying a mask value
i.e. it's possible to create a filter rule for an entire subnet of IP
addresses or a range of tcp/udp ports, etc.
We went through the existing filtering support (ethertype_filter,
syn_filter, ntuple_filter, flow_director) and have some questions on how
to accommodate the various h/w filtering features supported by Chelsio T5
by extending DPDK filtering support.
Some of the features that we would like to accommodate in DPDK filtering
are:
1. Add a new action 'switch' that will:
* Allow re-direction to different ports in hardware.
Also, for such a rule, additionally support below:
* Allow source mac/destination mac and vlan header re-writing to be
done by the hardware.
* Allow re-write of TCP/IP headers to perform NAT in hardware.
2. Add ability to mask individual fields at a particular layer for each
filter in flow_director. For example, mask all ip packets coming from
a particular subnet mask and particular range of l4 ports for each
filter rule.
We would like to get some suggestions on how to proceed with adding the
above features.
Thanks,
Rahul
next reply other threads:[~2015-11-30 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 12:49 Rahul Lakkireddy [this message]
2015-11-30 13:43 ` Thomas Monjalon
2015-12-02 8:05 ` Rahul Lakkireddy
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=20151130124943.GA15383@scalar.blr.asicdesigners.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=dev@dpdk.org \
--cc=felix@chelsio.com \
--cc=kumaras@chelsio.com \
--cc=nirranjan@chelsio.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).