Hi, has there been any consideration to introduce a non-spinning network driver 
(interrupt based), for the purpose of overcommitting CPUs in a virtualized 
environment?  This would obviously have reduced high-end performance but would 
allow for increased guest density (sharing of physical CPUs) on a host.

I am interested in adding support for this kind of operation, is there any 
interest in the community?

Thanks,

Mike.

Reply via email to