From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Felix Marti <felix@chelsio.com>,
Nirranjan Kirubaharan <nirranjan@chelsio.com>,
Kumar A S <kumaras@chelsio.com>
Subject: Re: [dpdk-dev] Query on Filtering Support in DPDK
Date: Wed, 2 Dec 2015 13:35:04 +0530 [thread overview]
Message-ID: <20151202080502.GA7710@scalar.blr.asicdesigners.com> (raw)
In-Reply-To: <2318875.uXDYP4N6Nj@xps13>
Hi Thomas,
On Monday, November 11/30/15, 2015 at 05:43:18 -0800, Thomas Monjalon wrote:
> Hi,
>
> 2015-11-30 18:19, Rahul Lakkireddy:
> > 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.
>
> You need to identify which API must change and what will be the ABI changes.
> Then please send a deprecation notice before December 11 in order to be part
> of the 2.2 release notes.
I am currently identifying the various API changes to support this and
also the ABI changes if any.
>
> If you have some RFC patches to send (at least the API changes), it would be
> a good discussion start.
I will try to post some RFC patches in 3-4 days time to get more
inputs/reviews on the approach.
Thanks,
Rahul.
prev parent reply other threads:[~2015-12-02 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 12:49 Rahul Lakkireddy
2015-11-30 13:43 ` Thomas Monjalon
2015-12-02 8:05 ` Rahul Lakkireddy [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=20151202080502.GA7710@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 \
--cc=thomas.monjalon@6wind.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).