DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vladislav Zolotarov <vladz@cloudius-systems.com>
To: Changchun Ouyang <changchun.ouyang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/6] Enable VF RSS for Niantic
Date: Sun, 21 Dec 2014 10:01:51 +0200	[thread overview]
Message-ID: <CAOYyTHbin=bRTB4EOn8egG1rfCZUc31DmWr7+VcPcfh-qCH_fg@mail.gmail.com> (raw)
In-Reply-To: <F52918179C57134FAEC9EA62FA2F9625119489D9@shsmsx102.ccr.corp.intel.com>

On Dec 19, 2014 3:35 AM, "Ouyang, Changchun" <changchun.ouyang@intel.com>
wrote:
>
> My response as below.
>
>
>
> From: Vlad Zolotarov [mailto:vladz@cloudius-systems.com]
> Sent: Thursday, December 18, 2014 9:06 PM
> To: dev@dpdk.org; Ouyang, Changchun
> Subject: Re: [PATCH 0/6] Enable VF RSS for Niantic
>
>
>
>
>
> On 12/18/14 12:11, Vlad Zolotarov wrote:
>>
>> From: Changchun Ouyang <changchun.ouyang@intel.com>
>>
>>
>>
>> This patch enables VF RSS for Niantic, which allow each VF having at
most 4 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~max vf num: 2 queues per VF;
>>
>>
>>
>> On host, to enable VF RSS functionality, mq mode should be set as
ETH_MQ_RX_VMDQ_RSS
>>
>> or ETH_MQ_RX_RSS mode, and SRIOV mode should be activated.
>>
>> It also needs config VF RSS information like hash function, RSS key, RSS
key length.
>
>
> This patch series is missing a few things:
>
> Taking into the consideration the number of Rx queues requested by a user
in the rte_eth_dev_configure().
>
> Changchun: yes, will have a v2 to consider it, as I say in my previous
response.

I must have joined the mailing list after your v2 series. I'll take a look
in the web for it.

>
> dev->dev_ops->reta_query used by a rte_eth_dev_rss_reta_query() is still
not initialized for a VF. Thus there is no way to query the RSS table
>
> Changchun: do you mean query rss table on guest?

Of course.

Niantic doesn’t have separate reta for a specific vf, the reta is shared by
pf and all vf.

AFAIK the reta is statically divided between all available functions.

So, first of all we need a way to know that is the size of a single VF
partition in order to know how many RSS queues may be configured.

Then we need an ability to query/set the contents of the corresponding reta
partition like we can for PF.

>
> Do you think of returning all reta contents for each vf make sense?  Or
any other insight here?
>
> rte_eth_dev_info_get() returns reta_size == 0 when called for a VF
function.
>
> Changchun:  same as above.
>
> Your insight here are welcome here.
>
> thanks
>
> Changchun
>
>

  reply	other threads:[~2014-12-21  8:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1418897516-25918-1-git-send-email-vladz@cloudius-systems.com>
2014-12-18 13:06 ` Vlad Zolotarov
2014-12-19  1:35   ` Ouyang, Changchun
2014-12-21  8:01     ` Vladislav Zolotarov [this message]
2014-12-24  6:37       ` Ouyang, Changchun
2014-12-24  8:01         ` Vlad Zolotarov
2014-12-15  2:56 Ouyang Changchun
2014-12-15 10:55 ` Bruce Richardson
2014-12-16  0:58   ` Ouyang, Changchun

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='CAOYyTHbin=bRTB4EOn8egG1rfCZUc31DmWr7+VcPcfh-qCH_fg@mail.gmail.com' \
    --to=vladz@cloudius-systems.com \
    --cc=changchun.ouyang@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).