From: David Miller <davem@davemloft.net>
To: dmitry@broadcom.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com, eilong@broadcom.com
Subject: Re: [PATCH net-next] bnx2x: Spread rx buffers between allocated queues
Date: Mon, 13 Sep 2010 20:04:41 -0700 (PDT) [thread overview]
Message-ID: <20100913.200441.258119112.davem@davemloft.net> (raw)
In-Reply-To: <1284306508.5534.1.camel@lb-tlvb-dmitry>
From: "Dmitry Kravkov" <dmitry@broadcom.com>
Date: Sun, 12 Sep 2010 17:48:28 +0200
> Default number of rx buffers will be divided equally
> between allocated queues. This will decrease amount of
> pre-allocated buffers on systems with multiple CPUs.
> User can override this behavior with ethtool -G.
> Minimum amount of rx buffers per queue set to 128.
>
> Reported-by: Eric Dumazet <eric.dumazet@gmail.com>
>
> Signed-off-by: Dmitry Kravkov <dmitry@broadcom.com>
> Signed-off-by: Eilon Greenstein <eilong@broadcom.com>
Applied, thank you.
prev parent reply other threads:[~2010-09-14 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 15:48 [PATCH net-next] bnx2x: Spread rx buffers between allocated queues Dmitry Kravkov
2010-09-14 3:04 ` David Miller [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=20100913.200441.258119112.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dmitry@broadcom.com \
--cc=eilong@broadcom.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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).