Netdev List
 help / color / mirror / Atom feed
From: Ron Mercer <ron.mercer@qlogic.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, ron.mercer@qlogic.com
Subject: [net-next PATCH 0/3] qlge: Allow running MSIx with fewer vectors.
Date: Thu, 27 Aug 2009 14:02:08 -0700	[thread overview]
Message-ID: <1251406931-15107-1-git-send-email-ron.mercer@qlogic.com> (raw)

Hello Dave and All,

The purpose of this patch series is to allow MSIx usage on
platforms where vector availability is limited.  The change is to
move broadcast/multicast/firmware event processing from a dedicated
'default' ring into the first RSS ring, and move TX completion
processing into NAPI context.

These patches change the rx_ring to MSIx vector mapping as follows:

FROM-
- 1 x default rx_ring (broadcast/multicast/firmware events)
- cpu_count x RSS rx_rings
- cpu_count x TX completion rx_rings.

We then attempt to allocate a vector for each rx_ring.  If it fails then
we drop down to MSI/Legacy single interrupt.  This is not efficient.


TO-
1) Get rid of dedicated default rx_ring and add it's extra functionality
	to the first RSS ring.
2) Allocate one RSS ring for each MSIX vector.
3) Allocate one TX completion ring for each CPU.
4) Move TX completion ring processing to NAPI context.

Each interrupt will start NAPI to process it's RSS ring and
and one or more TX completion rx_rings.

Regards,
Ron Mercer



             reply	other threads:[~2009-08-27 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 21:02 Ron Mercer [this message]
2009-08-27 21:02 ` [net-next PATCH 1/3] qlge: Get rid of 'default' rx_ring type Ron Mercer
2009-08-27 21:02 ` [net-next PATCH 2/3] qlge: Allow running MSIx with fewer vectors Ron Mercer
2009-08-27 21:02 ` [net-next PATCH 3/3] qlge: Move TX completions from workqueue to NAPI Ron Mercer
2009-08-29  6:23 ` [net-next PATCH 0/3] qlge: Allow running MSIx with fewer vectors 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=1251406931-15107-1-git-send-email-ron.mercer@qlogic.com \
    --to=ron.mercer@qlogic.com \
    --cc=davem@davemloft.net \
    --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