From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: overcommitting CPUs Date: Tue, 26 Aug 2014 09:38:37 -0700 Message-ID: <20140826093837.4e3d1d4b@urahara> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "Michael Marchetti" Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Tue, 26 Aug 2014 16:27:14 +0000 "Michael Marchetti" wrote: > 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. Better to implement a NAPI like algorithm that adapts from poll to interrupt.