DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: Vlad Zolotarov <vladz@cloudius-systems.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Avi Kivity <avi@cloudius-systems.com>,
	Gleb Natapov <gleb@cloudius-systems.com>
Subject: Re: [dpdk-dev] DPDK RSS support for ixgbevf PMD
Date: Fri, 19 Dec 2014 01:17:56 +0000	[thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F9625119489AD@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <5492AD87.8080401@cloudius-systems.com>

Hi ,

> -----Original Message-----
> From: Vlad Zolotarov [mailto:vladz@cloudius-systems.com]
> Sent: Thursday, December 18, 2014 6:34 PM
> To: Ouyang, Changchun; Thomas Monjalon
> Cc: dev@dpdk.org; Avi Kivity; Gleb Natapov
> Subject: Re: [dpdk-dev] DPDK RSS support for ixgbevf PMD
> 
> 
> On 12/18/14 03:32, Ouyang, Changchun wrote:
> > Hi
> >
> >> -----Original Message-----
> >> From: Vlad Zolotarov [mailto:vladz@cloudius-systems.com]
> >> Sent: Wednesday, December 17, 2014 4:47 PM
> >> To: Ouyang, Changchun; Thomas Monjalon
> >> Cc: dev@dpdk.org; Avi Kivity; Gleb Natapov
> >> Subject: Re: [dpdk-dev] DPDK RSS support for ixgbevf PMD
> >>
> >>
> >> On 12/17/14 03:03, Ouyang, Changchun wrote:
> >>> Hi ,
> >>>
> >>>> -----Original Message-----
> >>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Vlad
> Zolotarov
> >>>> Sent: Tuesday, December 16, 2014 11:36 PM
> >>>> To: Thomas Monjalon
> >>>> Cc: dev@dpdk.org; Avi Kivity; Gleb Natapov
> >>>> Subject: Re: [dpdk-dev] DPDK RSS support for ixgbevf PMD
> >>>>
> >>>>
> >>>> On 12/15/14 22:33, Thomas Monjalon wrote:
> >>>>> 2014-12-15 21:11, Vladislav Zolotarov:
> >>>>>> Hi,
> >>>>>> I'm running an ixgbevf PMD on an AWS guests with extended
> >>>>>> networking (SR-IOV functions of 82599 Intel's NIC) and noticed
> >>>>>> that even in the current git tree there is no support for a
> >>>>>> multi-queue in this
> >> PMD:
> >>>>>> reta size returned by rte_eth_dev_info_get() call is 0, while
> >>>>>> max_rx_queues and max_tx_queues are both 4.
> >>>>>>
> >>>>>> Linux ixgbevf-2.15.3 driver on the other hand successfully
> >>>>>> initializes 2 RSS queues: for some reason it always limits the
> >>>>>> number of
> >>>> RSS queues by 2.
> >>>>>> ixgbevf_main.c: line 2539
> >>>>>> u16 rss = min_t(u16, num_online_cpus(), 2);
> >>>>>>
> >>>>>> The above is strange since if MRQE is set to 1010b there are 4
> >>>>>> RSS queues available which seems to be the case in my AWS Guest.
> >>>>>>
> >>>>>> However, let's get back to DPDK. As I've mentioned above the
> >>>>>> SR-IOV function i have is RSS capable (to be 100% sure I've
> >>>>>> verified both queues are receiving packets in a multi-socket TCP
> >>>>>> test). And it's a shame I can't utilize it with a DPDK.
> >>>>> Yes, it is not yet supported.
> >>>>> But a patch was recently sent:
> >>>>> 	http://dpdk.org/ml/archives/dev/2014-December/010028.html
> >>>> Applying this patchset seems to break the NIC fast path
> >>>> functionality of a AWS Guest NIC.
> >>>> I'm still debugging it - will update u as soon as I have more specific info.
> >> Hi, thanks for tips but I have a question below.
> >>
> >>> Pls make sure enabling and using 4 queues on guest
> >> Why should I enable all 4? Won't any number below or equal 4 work if
> >> (!)
> >> 4 queues are available?
> >> Note that there is a 82599 mode when only 2 RSS queues are available
> >> per
> >> VF: MRQE=1011b.
> >>
> > Yes you are right, it could be 2 queues, the actual queue number per VF
> depends on the number of VF:
> > VF number from 1~32:     4 queues per VF;
> > VF number from 33~64:   2 queues per VF;
> > The queue number is determined by the vf number at the pf init stage,
> > If pf setup 4 queues for each vf and distribute packets to 4 queues,
> > but vf only poll 1 or 2 queue, Then packets in other queues will be lost.
> > You can try to poll 4 queues firstly to debug your issue.
> 
> Sure. When I hardcoded the queues number to 4 all works like a charm.
> The problem is that we can't leave it this way. I've posted some comments to
> your patches (0 and 5). Since I've joined the list after the patches have been
> sent I had to paste the patches bodies into my email and they will most like
> not appear in the thread of the original series.
> I hope this won't be a big problem... ;)
> 
Yes, I have seen your comments there, and respond it already, let's use that thread to discuss from now on.

Thanks
Changchun

      reply	other threads:[~2014-12-19  1:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 19:11 Vladislav Zolotarov
2014-12-15 20:33 ` Thomas Monjalon
2014-12-15 20:45   ` Dor Laor
2014-12-15 21:04     ` [dpdk-dev] DPDK on OSv (was: RSS for ixgbevf) Thomas Monjalon
2014-12-15 23:04       ` Dor Laor
2014-12-16 15:36   ` [dpdk-dev] DPDK RSS support for ixgbevf PMD Vlad Zolotarov
2014-12-17  1:03     ` Ouyang, Changchun
2014-12-17  8:46       ` Vlad Zolotarov
2014-12-18  1:32         ` Ouyang, Changchun
2014-12-18 10:33           ` Vlad Zolotarov
2014-12-19  1:17             ` Ouyang, Changchun [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=F52918179C57134FAEC9EA62FA2F9625119489AD@shsmsx102.ccr.corp.intel.com \
    --to=changchun.ouyang@intel.com \
    --cc=avi@cloudius-systems.com \
    --cc=dev@dpdk.org \
    --cc=gleb@cloudius-systems.com \
    --cc=thomas.monjalon@6wind.com \
    --cc=vladz@cloudius-systems.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).