Bug 699501

Summary: [RFE] qmfv2 must provide mainloop integration
Product: Red Hat Enterprise Linux 6 Reporter: Steven Dake <sdake>
Component: qpid-qmfAssignee: Ken Giusti <kgiusti>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1Keywords: FutureFeature
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-26 15:36:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Steven Dake 2011-04-25 19:53:34 UTC 
Description of problem:
qmfv2 does not provide a way to determine via a pollable file descriptor if a new event is available.

Version-Release number of selected component (if applicable):
rhel 6.1

How reproducible:
100%

Steps to Reproduce:
1. no api present
2.
3.
  
Actual results:
must simulate a pollable file descriptor by creating a timer to poll on a time interval to check for new events.

Expected results:
An api to get a pollable file descriptor should be made available.  When this pollable fd has a POLLIN event, a following event retrieval should result in an event without any delay related to timers for good high performance operation.

Additional info:

Workaround involves starting a timer to "poll" the event list via qmfv2.  Need a file descriptor to let the kernel do the polling so our apps don't chew cpu in cloud environments.
Comment 2 RHEL Program Management 2011-04-26 06:01:18 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 3 Steven Dake 2011-04-26 15:36:20 UTC 
bugzilla had an outage but submitted this bug twice - closing this one as a dup.

*** This bug has been marked as a duplicate of bug 699499 ***