netdev - [net-next PATCH 0/3] qlge: Allow running MSIx with fewer vectors.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Aug 2009 14:02:08 -0700
From:	Ron Mercer <ron.mercer@...gic.com>
To:	davem@...emloft.net
Cc:	netdev@...r.kernel.org, ron.mercer@...gic.com
Subject: [net-next PATCH 0/3] qlge: Allow running MSIx with fewer vectors.

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

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html