netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 4/8] be2net: SRIOV Queue distribution should factor in EQ-count of VFs
Date: Tue, 2 Feb 2016 17:30:48 +0300	[thread overview]
Message-ID: <56B0BD98.50809@cogentembedded.com> (raw)
In-Reply-To: <1454408435-11575-5-git-send-email-sriharsha.basavapatna@broadcom.com>

Hello.

On 2/2/2016 1:20 PM, Sriharsha Basavapatna wrote:

> The SRIOV resource distribution logic for RX/TX queue counts is not optimal
> when a small number of VFs are enabled. It does not take into account the
> VF's EQ count while computing the queue counts. Because of this, the VF
> gets a large number of queues, though it doesn't have sufficient EQs,
> resulting in wasted queue resources. And the PF gets a smaller share of
> queues though it has more EQs. Fix this by capping the VF queue count at
> its EQ count.
>
> Signed-off-by: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
> ---
>   drivers/net/ethernet/emulex/benet/be.h      |  4 ++++
>   drivers/net/ethernet/emulex/benet/be_main.c | 15 ++++++---------
>   2 files changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/net/ethernet/emulex/benet/be.h b/drivers/net/ethernet/emulex/benet/be.h
> index cf83783..f33d73c 100644
> --- a/drivers/net/ethernet/emulex/benet/be.h
> +++ b/drivers/net/ethernet/emulex/benet/be.h
> @@ -89,6 +89,10 @@
>   #define BE3_MAX_TX_QS		16
>   #define BE3_MAX_EVT_QS		16
>   #define BE3_SRIOV_MAX_EVT_QS	8
> +#define	SH_VF_MAX_NIC_EQS	3	/* Skyhawk VFs can have a max of 4 EQs

    Other #define's seem to have a space after them, not tab...

> +					 * and at least 1 is granted to either
> +					 * SURF/DPDK
> +					 */
>
>   #define MAX_RSS_IFACES		15
>   #define MAX_RX_QS		32
[...]

MBR, Sergei

  reply	other threads:[~2016-02-02 14:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 10:20 [PATCH net-next 0/8] be2net patch-set Sriharsha Basavapatna
2016-02-02 10:20 ` [PATCH net-next 1/8] be2net: return error status from be_set_phys_id() Sriharsha Basavapatna
2016-02-02 10:20 ` [PATCH net-next 2/8] be2net: check for INSUFFICIENT_PRIVILEGES error Sriharsha Basavapatna
2016-02-02 10:20 ` [PATCH net-next 3/8] be2net: Fix be_vlan_rem_vid() to check vlan id being removed Sriharsha Basavapatna
2016-02-02 10:20 ` [PATCH net-next 4/8] be2net: SRIOV Queue distribution should factor in EQ-count of VFs Sriharsha Basavapatna
2016-02-02 14:30   ` Sergei Shtylyov [this message]
2016-02-02 15:41     ` Sriharsha Basavapatna
2016-02-02 16:41       ` Sergei Shtylyov
2016-02-02 10:20 ` [PATCH net-next 5/8] be2net: Don't run ethtool self-tests for VFs Sriharsha Basavapatna
2016-02-02 10:20 ` [PATCH net-next 6/8] benet: Fix Lancer error recovery Sriharsha Basavapatna
2016-02-02 10:20 ` [PATCH net-next 7/8] benet: Add retry in case of error recovery failure Sriharsha Basavapatna
2016-02-02 10:20 ` [PATCH net-next 8/8] benet: Fix interval calculation in interrupt moderation Sriharsha Basavapatna

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=56B0BD98.50809@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=netdev@vger.kernel.org \
    --cc=sriharsha.basavapatna@broadcom.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).