From: Joe Perches <joe@perches.com>
To: madalin.bucur@freescale.com
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, scottwood@freescale.com,
igal.liberman@freescale.com, ppc@mindchasers.com,
pebolle@tiscali.nl, joakim.tjernlund@transmode.se
Subject: Re: [PATCH 03/10] dpaa_eth: add configurable bpool thresholds
Date: Wed, 22 Jul 2015 10:47:08 -0700 [thread overview]
Message-ID: <1437587228.20787.26.camel@perches.com> (raw)
In-Reply-To: <1437581806-17420-3-git-send-email-madalin.bucur@freescale.com>
On Wed, 2015-07-22 at 19:16 +0300, Madalin Bucur wrote:
> Allow the user to tweak the refill threshold and the total number
> of buffers in the buffer pool. The provided values are for one CPU.
Any value in making these module parameters instead?
> +config FSL_DPAA_ETH_MAX_BUF_COUNT
> + int "Maximum number of buffers in private bpool"
> + range 64 2048
> + default "128"
> + ---help---
> + The maximum number of buffers to be by default allocated in the DPAA-Ethernet private port's
> + buffer pool. One needn't normally modify this, as it has probably been tuned for performance
> + already. This cannot be lower than DPAA_ETH_REFILL_THRESHOLD.
> +
> +config FSL_DPAA_ETH_REFILL_THRESHOLD
> + int "Private bpool refill threshold"
> + range 32 FSL_DPAA_ETH_MAX_BUF_COUNT
> + default "80"
> + ---help---
> + The DPAA-Ethernet driver will start replenishing buffer pools whose count
> + falls below this threshold. This must be related to DPAA_ETH_MAX_BUF_COUNT. One needn't normally
> + modify this value unless one has very specific performance reasons.
> +
> config FSL_DPAA_CS_THRESHOLD_1G
> hex "Egress congestion threshold on 1G ports"
> range 0x1000 0x10000000
next prev parent reply other threads:[~2015-07-22 17:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 16:16 [PATCH 01/10] devres: add devm_alloc_percpu() Madalin Bucur
2015-07-22 16:16 ` [PATCH 02/10] dpaa_eth: add support for DPAA Ethernet Madalin Bucur
2015-07-22 16:16 ` [PATCH 03/10] dpaa_eth: add configurable bpool thresholds Madalin Bucur
2015-07-22 16:16 ` [PATCH 04/10] dpaa_eth: add support for S/G frames Madalin Bucur
2015-07-22 16:16 ` [PATCH 05/10] dpaa_eth: add driver's Tx queue selection mechanism Madalin Bucur
2015-07-22 16:16 ` [PATCH 06/10] dpaa_eth: add ethtool functionality Madalin Bucur
2015-07-22 16:16 ` [PATCH 07/10] dpaa_eth: add sysfs exports Madalin Bucur
2015-07-22 16:16 ` [PATCH 08/10] dpaa_eth: add debugfs counters Madalin Bucur
2015-07-22 16:16 ` [PATCH 09/10] dpaa_eth: add debugfs entries Madalin Bucur
2015-07-22 16:16 ` [PATCH 10/10] dpaa_eth: add trace points Madalin Bucur
2015-07-22 17:47 ` Joe Perches [this message]
2015-07-24 15:49 ` [PATCH 03/10] dpaa_eth: add configurable bpool thresholds Madalin-Cristian Bucur
2015-07-26 23:35 ` David Miller
2015-07-27 12:54 ` Madalin-Cristian Bucur
2015-07-22 17:37 ` [PATCH 02/10] dpaa_eth: add support for DPAA Ethernet Joe Perches
2015-07-24 15:45 ` Madalin-Cristian Bucur
2015-07-27 18:59 ` Scott Wood
2015-07-29 14:15 ` Joakim Tjernlund
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=1437587228.20787.26.camel@perches.com \
--to=joe@perches.com \
--cc=igal.liberman@freescale.com \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=ppc@mindchasers.com \
--cc=scottwood@freescale.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).