From: David Miller <davem@davemloft.net>
To: sathya.perla@emulex.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] be2net: create RSS rings even in multi-channel configs
Date: Sun, 22 Jan 2012 14:25:07 -0500 (EST) [thread overview]
Message-ID: <20120122.142507.94851514947863308.davem@davemloft.net> (raw)
In-Reply-To: <1327041244-427-1-git-send-email-sathya.perla@emulex.com>
From: Sathya Perla <sathya.perla@emulex.com>
Date: Fri, 20 Jan 2012 12:04:04 +0530
> Currently RSS rings are not created in a multi-channel config.
> RSS rings can be created on one (out of four) interfaces per port in a
> multi-channel config. Doing this insulates the driver from a FW bug wherin
> multi-channel config is wrongly reported even when not enabled. This also
> helps performance in a multi-channel config, as one interface per port gets
> RSS rings.
>
> Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
Applied.
prev parent reply other threads:[~2012-01-22 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 6:34 [PATCH] be2net: create RSS rings even in multi-channel configs Sathya Perla
2012-01-22 19:25 ` 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=20120122.142507.94851514947863308.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@emulex.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).