Bug 451053 - s2io tx_fifo_num doesn't spread interrupt loads
s2io tx_fifo_num doesn't spread interrupt loads
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
5.2
All Linux
low Severity low
: rc
: ---
Assigned To: Veaceslav Falico
Red Hat Kernel QE team
: OtherQA
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-12 12:06 EDT by Andrew Hecox
Modified: 2014-09-30 19:44 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-12 22:08:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew Hecox 2008-06-12 12:06:10 EDT
the s2io driver allows you to create up to 8 tx_fifo's. However, all interrupts
are observed to go a single queue (#1). In the -29 version of the driver
multiqueue support was added. It appears this would enable spreading interrupts
across all tx_fifo's. 

Benchmarking for small packet sizes is CPU bound; allowing multiple CPUs to
assist in interrupt processing would improve the problem.
Comment 1 Michal Schmidt 2009-11-30 02:52:08 EST
A test kernel build with s2io backported from current upstream is now
available: https://brewweb.devel.redhat.com/taskinfo?taskID=2108561
I also uploaded it to a publicly accessible location:
http://disk.jabbim.cz/michich@jabber.cz/s2io/
Could you please test it?
Comment 3 John Feeney 2013-11-12 22:08:04 EST
This Bugzilla has been reviewed by Red Hat and is not planned on being
addressed in Red Hat Enterprise Linux 5, and therefore is being closed.
If this bug is critical to production systems, please contact your Red
Hat support representative and provide a sufficient business justification
in order to re-open it.

Note You need to log in before you can comment on or make changes to this bug.