From: Gal Sagie <gal.sagie@gmail.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] FlowDirector Rules for TX packets
Date: Fri, 27 Mar 2015 17:36:50 +0300 [thread overview]
Message-ID: <CAG9LJa55CGPd1fJirSEHtcOt4Zq32qRTm7D6gre=aKsVpNAYOQ@mail.gmail.com> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891263233A0FA@IRSMSX108.ger.corp.intel.com>
Thanks for the answer Cristian,
Is there any TX-side packet filtering feature? (or one planned)
(I do think it make sense in virtualised environments)
Thanks
Gal.
On Fri, Mar 27, 2015 at 5:20 PM, Dumitrescu, Cristian <
cristian.dumitrescu@intel.com> wrote:
> Hi Gal,
>
> No, flow director is just an RX-side packet filtering NIC feature.
>
> Regards,
> Cristian
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gal Sagie
> > Sent: Friday, March 27, 2015 10:44 AM
> > To: <dev@dpdk.org>
> > Subject: [dpdk-dev] FlowDirector Rules for TX packets
> >
> > Hello All,
> >
> > I can define drop filter rules for RX packets using FlowDirector.
> > Support for configuring this from CLI is also available using ethtool
> with
> > the --config-ntuple option
> >
> > I am wondering, does FlowDirector has any support to drop TX packets?
> > (Meaning that i can define rules which are if matched in the TX side will
> > not send the packets out)
> >
> > At least from ethtool it doesn't seems like this is supported..
> > Any idea?
> >
> > Thanks
> > Gal.
>
--
Best Regards ,
The G.
prev parent reply other threads:[~2015-03-27 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 10:43 Gal Sagie
2015-03-27 14:20 ` Dumitrescu, Cristian
2015-03-27 14:36 ` Gal Sagie [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='CAG9LJa55CGPd1fJirSEHtcOt4Zq32qRTm7D6gre=aKsVpNAYOQ@mail.gmail.com' \
--to=gal.sagie@gmail.com \
--cc=cristian.dumitrescu@intel.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).