DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Kamraan Nasim <knasim@sidebandnetworks.com>
Cc: dev@dpdk.org, Ean Houts <ehouts@sidebandnetworks.com>,
	Jun Du <jdu@sidebandnetworks.com>
Subject: Re: [dpdk-dev] Does I210 NIC support Flow director filters?
Date: Fri, 16 Jan 2015 17:31:59 +0000	[thread overview]
Message-ID: <20150116173158.GA9528@bricha3-MOBL3> (raw)
In-Reply-To: <CAPrTskgx8NOdxKKVjNiw50wumcN8gMxE2k_6+4ofGV8BdPbiDQ@mail.gmail.com>

On Fri, Jan 16, 2015 at 11:42:42AM -0500, Kamraan Nasim wrote:
> Hi Bruce,
> Perhaps this can be worked around by setting  rx_drop_en in the
> rte_eth_rxconf <http://dpdk.org/doc/api/structrte__eth__rxconf.html> and
> using small values for number of rx descripters so that the NIC drops when
> it is out of RX descriptors for that queue?
> 
> As long as NIC can still provide q_ipackets/q_errors then this might be
> faster than doing a RX in software and drop.
> 
> --Kam

Yes, so long as packets dropped for that queue are counted against that queue,
then yes.

/Bruce

> 
> On Fri, Jan 16, 2015 at 5:56 AM, Bruce Richardson <
> bruce.richardson@intel.com> wrote:
> 
> > On Thu, Jan 15, 2015 at 08:06:52PM -0500, Kamraan Nasim wrote:
> > > >>> update the RSS RETA table so that traffic doesn't get sent
> > > >> to that queue via RSS. Is that what you are asking?
> > >
> > > Thanks Bruce, that's exactly it.  Basically each filter will forward
> > > traffic to a unique RSS queue which can allow me to calculate filter
> > match
> > > statistics for that queue(or filter). At that point I would like to drop
> > > the filtered packet. Is there any way to drop the filtered packet in the
> > > RSS queue without doing a rte_eth_rx_burst() and dropping it then?
> > >
> > > --Kam
> > >
> > I don't believe there is any other way to drop them from the queue other
> > than
> > RX and drop. It's not the most efficient way to do so (since you have to
> > allocate,
> > fill and free an mbuf), but it's the only way that an app can do so without
> > adding new functions to the driver(s).
> >
> > /Bruce
> >

      reply	other threads:[~2015-01-16 17:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14  4:21 Kamraan Nasim
2015-01-14  7:42 ` Zhang, Helin
2015-01-14 10:27 ` Bruce Richardson
2015-01-14 21:59   ` Kamraan Nasim
2015-01-15 14:44     ` Bruce Richardson
2015-01-16  1:06       ` Kamraan Nasim
2015-01-16 10:56         ` Bruce Richardson
2015-01-16 16:42           ` Kamraan Nasim
2015-01-16 17:31             ` Bruce Richardson [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=20150116173158.GA9528@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ehouts@sidebandnetworks.com \
    --cc=jdu@sidebandnetworks.com \
    --cc=knasim@sidebandnetworks.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).