From: "Zhang, Helin" <helin.zhang@intel.com>
To: David Marchand <david.marchand@6wind.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Pei, Yulong" <yulong.pei@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] i40e: Enlarge the number of supported queues
Date: Tue, 22 Sep 2015 06:36:06 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A900F1F@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CALwxeUtyF9M6J1PyZy0UG1VC-bQ5SbyeGfrZ_3m1=SojjNN5sw@mail.gmail.com>
Hi David
PF, VFs VMDq, FD on the same port share the queues, actually we can know the total number of the queues, the maximum number of queues may vary depends on how they will be used with PF, VF, VMDq AND FD.
So the users will define the number for each, the code will just check the total number of them and make sure not exceed that.
Regards,
Helin
Note: just resend it with plain text format.
From: David Marchand [mailto:david.marchand@6wind.com]
Sent: Monday, September 21, 2015 3:42 PM
To: Zhang, Helin; Richardson, Bruce
Cc: dev@dpdk.org; Pei, Yulong
Subject: Re: [dpdk-dev] [PATCH 2/2] i40e: Enlarge the number of supported queues
Hello Helin, Bruce,
On Sun, Sep 20, 2015 at 4:51 PM, Helin Zhang <helin.zhang@intel.com> wrote:
It enlarges the number of supported queues to hardware allowed
maximum. There was a software limitation of 64 per physical port
which is not reasonable.
I looked at the commit that introduced this limitation, can't we just get rid of this ?
The primary process should know the current max queue number and initialises the array properly before any secondary process tries to set any callback, or tries to call rx/tx functions.
Did I miss something ?
--
David Marchand
next prev parent reply other threads:[~2015-09-22 6:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 14:51 [dpdk-dev] [PATCH 0/2] i40e: enlarge " Helin Zhang
2015-09-20 14:51 ` [dpdk-dev] [PATCH 1/2] i40e: adjust the number of queues for RSS Helin Zhang
2015-09-20 14:51 ` [dpdk-dev] [PATCH 2/2] i40e: Enlarge the number of supported queues Helin Zhang
2015-09-21 7:41 ` David Marchand
2015-09-21 8:15 ` Zhang, Helin
2015-09-22 6:36 ` Zhang, Helin [this message]
2015-10-19 8:29 ` Wu, Jingjing
2015-10-19 8:37 ` Zhang, Helin
2015-10-22 7:28 ` [dpdk-dev] [PATCH v2 0/2] " Helin Zhang
2015-10-22 7:28 ` [dpdk-dev] [PATCH v2 1/2] i40e: adjust the number of queues for RSS Helin Zhang
2015-10-22 7:28 ` [dpdk-dev] [PATCH v2 2/2] i40e: Enlarge the number of supported queues Helin Zhang
2015-11-03 1:16 ` Thomas Monjalon
2015-11-03 2:49 ` Zhang, Helin
2015-10-22 15:36 ` [dpdk-dev] [PATCH v2 0/2] " Wu, Jingjing
2015-11-03 15:40 ` [dpdk-dev] [PATCH v3 " Helin Zhang
2015-11-03 15:40 ` [dpdk-dev] [PATCH v3 1/2] i40e: adjust the number of queues for RSS Helin Zhang
2015-11-03 15:40 ` [dpdk-dev] [PATCH v3 2/2] i40e: Enlarge the number of supported queues Helin Zhang
2015-11-03 21:59 ` [dpdk-dev] [PATCH v3 0/2] " Thomas Monjalon
2015-11-04 14:54 ` Traynor, Kevin
2015-11-05 0:39 ` Zhang, Helin
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A900F1F@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=yulong.pei@intel.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).