DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Navneet Rao <navneet.rao@oracle.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] flow_director_filter error!!
Date: Wed, 26 Aug 2015 07:27:56 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C7ED792@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <9c78ef3c-bc1f-4ceb-9f7d-2a0f12c4eea2@default>

Hi Navneet,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Navneet Rao
> Sent: Tuesday, August 25, 2015 9:27 PM
> To: Wu, Jingjing; Mcnamara, John; dev@dpdk.org
> Subject: Re: [dpdk-dev] flow_director_filter error!!
> 
> Hi Jingjing:
> 
> Thanks.
> 
> I did have the ethertype_filter ignore the mac_addr, and look at only
> ethertype filtyer and it still  got a "bad arguments" message :-(
> 
> testpmd>  ethertype_filter 0 add mac_ignr ethertype 0x0806 fwd queue 1
> Bad arguments

Yes, apparently the example is wrong. It misses the MAC address, after mac_ignr.
So it should be:

ethertype_filter 0 add mac_ignr 00:11:22:33:44:55 ethertype 0x0806 fwd queue 1

Regards,
Pablo

> 
> 
> 
> -----Original Message-----
> From: Wu, Jingjing [mailto:jingjing.wu@intel.com]
> Sent: Tuesday, August 25, 2015 6:55 AM
> To: Navneet Rao; Mcnamara, John; dev@dpdk.org
> Subject: RE: [dpdk-dev] flow_director_filter error!!
> 
> Hi, Navneet
> 
> I'm sorry for I have no idea about the NIC i540. Are you talking about X540?
> If X540, I guess you can't classify on the MAC-ADDRESS to different queue by
> ethertype filter. Because in the X540 datasheet the ethertype filter is
> described as below:
> " 7.1.2.3 L2 Ethertype Filters
> These filters identify packets by their L2 Ethertype, 802.1Q user priority and
> optionally assign them to a receive queue."
> 
> So the mac_address is not the filter's input.
> 
> Thanks
> Jingjing
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Navneet Rao
> > Sent: Friday, August 21, 2015 2:57 AM
> > To: Mcnamara, John; dev@dpdk.org
> > Subject: Re: [dpdk-dev] flow_director_filter error!!
> >
> > Thanks John.
> >
> > I am trying to setup/use the flow-director-filter on the i540.
> >
> > -- When I try to setup the flow-director-filter as per the example, I
> > am getting "bad arguments"!!!
> >      So decided to see if the flush command would work.
> >
> >
> > In the interim --- I am using ethertype filter to accomplish the following.
> > What I am trying to do is this --
> > Use 2 different i540 cards
> > Use the igb_uio driver.
> > Use the testpmd app.
> > Setup 5 different MAC-ADDRESSes on each port. (using the set mac_addr
> > command) Setup 5 different RxQs and TxQs on each port.
> > And then use the testpmd app to generate traffic..
> >
> > I am assuming that the testpmd app will now send and receive traffic
> > using the 5 different MAC_ADDRESSes..
> > On each port's receive I will now want to classify on the MAC-ADDRESS
> > and steer the traffic to different queues.
> >
> > Is there an example/reference on how to achieve this?
> >
> > Next, I would want to do "classify" on "flexbytes" and send/steer the
> > traffic to different queues using flow-director-filter.
> >
> > Thanks
> > -Navneet
> >
> >
> >
> >
> > -----Original Message-----
> > From: Mcnamara, John [mailto:john.mcnamara@intel.com]
> > Sent: Wednesday, August 19, 2015 3:39 PM
> > To: Navneet Rao; dev@dpdk.org
> > Subject: RE: [dpdk-dev] flow_director_filter error!!
> >
> > > -----Original Message-----
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Navneet Rao
> > > Sent: Tuesday, August 18, 2015 4:01 PM
> > > To:  HYPERLINK "mailto:dev@dpdk.org" dev@dpdk.org
> > > Subject: [dpdk-dev] flow_director_filter error!!
> > >
> > > After I start the testpmd app, I am flusing the flow_director_filter
> > > settings and get the following error -
> > >
> > >
> > >
> > > testpmd> flush_flow_director 0
> > >
> > > PMD: ixgbe_fdir_flush(): Failed to re-initialize FD table.
> > >
> > > flow director table flushing error: (Too many open files in system)
> >
> > Hi,
> >
> > Are you setting a flow director filter before flushing? If so, could you give
> an example.
> >
> > John.
> > --
> >

  reply	other threads:[~2015-08-26  7:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 23:00 Navneet Rao
2015-08-19 19:26 ` Navneet Rao
2015-08-20  7:17   ` Wu, Jingjing
2015-08-19 22:39 ` Mcnamara, John
2015-08-20 18:56   ` Navneet Rao
2015-08-25 13:55     ` Wu, Jingjing
2015-08-25 20:27       ` Navneet Rao
2015-08-26  7:27         ` De Lara Guarch, Pablo [this message]
2015-08-26 17:11           ` Navneet Rao
2015-08-28  0:35           ` Navneet Rao
2015-08-28 22:11             ` Navneet Rao
2015-08-28 22:50               ` Navneet Rao
2015-08-31 11:07               ` Mcnamara, John
2015-09-02  0:09                 ` Navneet Rao

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=E115CCD9D858EF4F90C690B0DCB4D8973C7ED792@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=navneet.rao@oracle.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).