From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: Ilan Borenshtein <ilan@asocstech.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Signature filter for virtual function
Date: Tue, 19 Aug 2014 07:40:49 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F8AD9AAA@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <7241f60d228f4a4dae39ed26f316d81c@AMSPR06MB086.eurprd06.prod.outlook.com>
Are you talking about 82599?
I have no plan to support this currently. But I don't know there may be volunteers who is planning for it. I guess it also be great if you are eager to contribute to it.
> -----Original Message-----
> From: Ilan Borenshtein [mailto:ilan@asocstech.com]
> Sent: Monday, August 18, 2014 3:17 PM
> To: Wu, Jingjing; dev@dpdk.org
> Subject: RE: Signature filter for virtual function
>
> Looking for director packet to different queues in a VF.
> Will it be implemented in future releases ?
>
> -----Original Message-----
> From: Wu, Jingjing [mailto:jingjing.wu@intel.com]
> Sent: Monday, August 18, 2014 3:40 AM
> To: Ilan Borenshtein; dev@dpdk.org
> Subject: RE: Signature filter for virtual function
>
> Could you explain what exactly you want? Director packet to a VF? Or director packet to
> different queue in a VF?
>
> For the first one, I think if you know which queue the VF is using, the flow director can do it
> (it's my understanding, haven't try).
> But for the latter, I have no idea which way can be used instead.
>
>
> > -----Original Message-----
> > From: Ilan Borenshtein [mailto:ilan@asocstech.com]
> > Sent: Sunday, August 17, 2014 3:34 PM
> > To: Wu, Jingjing; dev@dpdk.org
> > Subject: RE: Signature filter for virtual function
> >
> > Hi,
> >
> > Is there any other way except of the Flow director to use the different Rx queues by a VF ?
> > Will the next versions support flow director for VF ?
> >
> > Thanks,
> > Ilan B
> >
> >
> > -----Original Message-----
> > From: Wu, Jingjing [mailto:jingjing.wu@intel.com]
> > Sent: Friday, August 15, 2014 10:51 AM
> > To: Ilan Borenshtein; dev@dpdk.org
> > Subject: RE: Signature filter for virtual function
> >
> > Hi
> >
> > Flow director is not supported on VF now.
> > I think this may be the reason why ENOTSUP is returned.
> >
> >
> > > -----Original Message-----
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ilan
> > > Borenshtein
> > > Sent: Thursday, August 14, 2014 8:34 PM
> > > To: dev@dpdk.org
> > > Subject: [dpdk-dev] Signature filter for virtual function
> > >
> > > Hello,
> > >
> > > I'm trying to configure the flow director of VF 82599 port using
> > > rte_eth_dev_fdir_add_signature_filter ().
> > > The function returns with ENOTSUP.
> > > Doe's flow director supported for VF ?
> > > What can be the reason for ENOTSUP ?
> > >
> > > Thanks,
> > > Ilan B
next prev parent reply other threads:[~2014-08-19 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 12:33 Ilan Borenshtein
2014-08-15 7:50 ` Wu, Jingjing
2014-08-17 7:34 ` Ilan Borenshtein
2014-08-18 0:40 ` Wu, Jingjing
2014-08-18 7:16 ` Ilan Borenshtein
2014-08-19 7:40 ` Wu, Jingjing [this message]
2014-08-19 8:08 ` Ilan Borenshtein
2014-08-19 10:58 ` Vladimir Medvedkin
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=9BB6961774997848B5B42BEC655768F8AD9AAA@SHSMSX104.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=ilan@asocstech.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).