From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "Zhang, Helin" <helin.zhang@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] i40e queues per VF
Date: Tue, 21 Mar 2017 06:01:00 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810CF8740@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <6154321.GLCpcWPPOA@xps13>
> > This number is used as initialization time to allocate queue number
> > for PF/VF for HW's queue pool. Will add more description in i40e.rst.
>
> The description "Number of queues reserved for each SR-IOV VF" seems
> partially wrong. Please explain it is a queue pair.
>
OK. Sure.
[......]
> > >
> > > Is there something to configure the number of queues when creating
> > > VF with the kernel driver?
> >
> > In kernel driver, it seems at most only 4 queues are supported. That's
> > Why we add build-time config option to make more queues are possible.
>
> If we can create 16 queue pairs, why restrict the default configuration to 4?
> Why is it a build-time config option?
If we allocate 16 queue pairs by default, then the number of VFs will be limited
Because of the entire queue resources on NIC.
Anyway, I will update doc on this part. Sorry for the delay because of trip.
Thanks
Jingjing
prev parent reply other threads:[~2017-03-21 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 10:07 Thomas Monjalon
2017-02-16 10:03 ` Xu, Qian Q
2017-02-16 13:58 ` Wu, Jingjing
2017-02-16 14:55 ` Thomas Monjalon
2017-03-08 11:25 ` Thomas Monjalon
2017-03-14 9:31 ` Thomas Monjalon
2017-03-21 6:01 ` Wu, Jingjing [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=9BB6961774997848B5B42BEC655768F810CF8740@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.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).