Bug 692406

Summary:	[RFE] Provide netchannel2 and multi-queue support in Xen
Product:	Red Hat Enterprise Linux 5	Reporter:	J.H.M. Dassen (Ray) <rdassen>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.6	CC:	leiwang, minovotn, mrezanin, pbonzini, qwan, rbinkhor, sputhenp, xen-maint, yuzhang
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-29 09:41:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	699616

Description J.H.M. Dassen (Ray) 2011-03-31 09:25:16 UTC

2. What is the nature and description of the request?

implement netchannel2 and multi-queue support on XEN

   3. Why does the customer need this?

 destribute network load across CPUs, hence improved performance.

   4. How would the customer like to achieve this?

It is available on upstream XEN v4, http://blog.xen.org/index.php/2010/04/13/xen-4-0-feature-list/ 

   5. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.

check /proc/interrupts and make sure interrupts are destributed across
multi-queeus.

   6. Is there already an existing RFE upstream or in Red Hat bugzilla?

no

   7. How quickly does this need resolved?

RHEL 5 minor release

   8. Does this request meet the RHEL Inclusion criteria

yes

   9. List the affected packages

xen, kernel-xen

  10. Would the customer be able to assist in testing this functionality if
implemented?

yes

Comment 8 Miroslav Rezanina 2011-06-29 09:41:07 UTC

Requested feature is too large and risky to be integrated by RHEL in current lifecycle state. So we decided to rejected this request and do not impelement requested feature.