From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org, benli@broadcom.com
Subject: Re: [PATCH 6/8] bnx2: Turn on multi rx rings.
Date: Thu, 19 Jun 2008 16:43:48 -0700 (PDT) [thread overview]
Message-ID: <20080619.164348.195675064.davem@davemloft.net> (raw)
In-Reply-To: <1213835132-5698-7-git-send-email-mchan@broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Wed, 18 Jun 2008 17:25:30 -0700
> Enable multiple rx rings if MSI-X vectors are available. We enable
> up to 7 rx rings.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
> Signed-off-by: Benjamin Li <benli@broadcom.com>
Applied to net-next-2.6
I hope that on the TX side you'll use some power-of-2
number of TX rings as this will make the SW flow hash
function less expensive to compute.
next prev parent reply other threads:[~2008-06-19 23:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 0:25 [PATCH 0/8] bnx2: Enable multi rx rings Michael Chan
2008-06-19 0:25 ` [PATCH 1/8] bnx2: Put tx ring variables in a separate struct Michael Chan
2008-06-19 23:39 ` David Miller
2008-06-19 0:25 ` [PATCH 2/8] bnx2: Put rx " Michael Chan
2008-06-19 23:39 ` David Miller
2008-06-19 0:25 ` [PATCH 3/8] bnx2: Optimize fast-path tx and rx work Michael Chan
2008-06-19 23:41 ` David Miller
2008-06-19 0:25 ` [PATCH 4/8] bnx2: Use one handler for all MSI-X vectors Michael Chan
2008-06-19 23:42 ` David Miller
2008-06-19 0:25 ` [PATCH 6/8] bnx2: Turn on multi rx rings Michael Chan
2008-06-19 23:43 ` David Miller [this message]
2008-06-19 0:25 ` [PATCH 7/8] bnx2: Cleanup error handling in bnx2_open() Michael Chan
2008-06-19 23:44 ` David Miller
2008-06-19 0:25 ` [PATCH 8/8] bnx2: Update driver version to 1.7.7 Michael Chan
2008-06-19 23:45 ` David Miller
[not found] ` <1213835132-5698-6-git-send-email-mchan@broadcom.com>
2008-06-19 23:42 ` [PATCH 5/8] bnx2: Update firmware to support multi rx rings David Miller
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=20080619.164348.195675064.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benli@broadcom.com \
--cc=mchan@broadcom.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).