From: "Dmitry Kravkov" <dmitry@broadcom.com>
To: "Tom Herbert" <therbert@google.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v4 09/10] bnx2x: Support for byte queue limits
Date: Tue, 29 Nov 2011 11:43:35 +0200 [thread overview]
Message-ID: <1322559815.25184.3.camel@lb-tlvb-dmitry> (raw)
In-Reply-To: <alpine.DEB.2.00.1111281821300.23758@pokey.mtv.corp.google.com>
On Mon, 2011-11-28 at 18:33 -0800, Tom Herbert wrote:
> Changes to bnx2x to use byte queue limits.
>
> Signed-off-by: Tom Herbert <therbert@google.com>
> ---
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 26 +++++++++++++++++++---
> 1 files changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c b/drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c
> index 8336c78..42ce566 100644
> --- a/drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c
> +++ b/drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c
> @@ -102,7 +102,8 @@ int load_count[2][3] = { {0} }; /* per-path: 0-common, 1-port0, 2-port1 */
> * return idx of last bd freed
> */
> static u16 bnx2x_free_tx_pkt(struct bnx2x *bp, struct bnx2x_fp_txdata *txdata,
> - u16 idx)
> + u16 idx, unsigned int *pkts_compl,
> + unsigned int *bytes_compl)
> {
> struct sw_tx_bd *tx_buf = &txdata->tx_buf_ring[idx];
> struct eth_tx_start_bd *tx_start_bd;
> @@ -159,6 +160,10 @@ static u16 bnx2x_free_tx_pkt(struct bnx2x *bp, struct bnx2x_fp_txdata *txdata,
>
> /* release skb */
> WARN_ON(!skb);
> + if (skb) {
likely statement will be usefull here, since we don't expect it to be
null
> + (*pkts_compl)++;
> + (*bytes_compl) += skb->len;
> + }
prev parent reply other threads:[~2011-11-29 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 2:33 [PATCH v4 09/10] bnx2x: Support for byte queue limits Tom Herbert
2011-11-29 9:43 ` Dmitry Kravkov [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=1322559815.25184.3.camel@lb-tlvb-dmitry \
--to=dmitry@broadcom.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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