From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH 1/2] kvm tools: Respect ISR status in virtio header Date: Sat, 7 May 2011 16:00:30 +0200 Message-ID: <20110507140030.GA2859@elte.hu> References: <1304735660-10844-1-git-send-email-asias.hejun@gmail.com> <20110507093027.GD27657@elte.hu> <4DC529E8.8030104@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Michael S. Tsirkin" , Rusty Russell , Mark McLoughlin , Anthony Liguori , Pekka Enberg , Cyrill Gorcunov , Sasha Levin , Prasad Joshi , kvm@vger.kernel.org To: Asias He Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:52912 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754618Ab1EGOAu (ORCPT ); Sat, 7 May 2011 10:00:50 -0400 Content-Disposition: inline In-Reply-To: <4DC529E8.8030104@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: * Asias He wrote: > BTW. The ping latency was caused by the movement of irq injection outside the > loop. Suppose we have 5 available buffers and only 1 buffer from tap device. > We will sleep on read without giving the buffer from tap to guest. The > latency will be huge in this case. > > while(virt_queue__available(vq)) { > ... > read(tap_fd) > ... > } > trigger_irq() But ... in one of the mails one of you claimed that even when moving the irq notification inside the loop (which we all agreed was necessary to avoid latencies!) the latencies would still occur during stress-tests. So something is still not understood here and could hit us anytime with any of the virtio drivers in the future and such bugs are not always so nice to debug like the latency problem here ... Thanks, Ingo