From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: updated: kvm networking todo wiki Date: Thu, 30 May 2013 16:48:29 +0930 Message-ID: <87fvx5kkai.fsf@rustcorp.com.au> References: <20130523085034.GA16142@redhat.com> <519F35B7.6010408@redhat.com> <20130524113542.GA7046@redhat.com> <8738tctrox.fsf@codemonkey.ws> <20130524140024.GA12024@redhat.com> <87li6yodgq.fsf@rustcorp.com.au> <87k3miq6sw.fsf@codemonkey.ws> <87r4gpkplc.fsf@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Stefan Hajnoczi Cc: kvm , "Michael S. Tsirkin" , netdev@vger.kernel.org, qemu-devel , Linux Virtualization , herbert@gondor.hengli.com.au, Anthony Liguori List-Id: virtualization@lists.linuxfoundation.org Stefan Hajnoczi writes: > On Thu, May 30, 2013 at 7:23 AM, Rusty Russell wrote: >> On the receive side, what can we do better than readv? If we need to >> return to userspace to tell the guest that we've got a new packet, we >> don't win on latency. We might reduce syscall overhead with a >> multi-dimensional readv to read multiple packets at once? > > Sounds like recvmmsg(2). Wow... the future is here, today! Thanks, Rusty. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:56704) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UhxYj-0001Z9-VD for qemu-devel@nongnu.org; Thu, 30 May 2013 03:46:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UhxYb-0006KC-Rr for qemu-devel@nongnu.org; Thu, 30 May 2013 03:46:05 -0400 Received: from ozlabs.org ([203.10.76.45]:58231) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UhxYb-0006Jp-CD for qemu-devel@nongnu.org; Thu, 30 May 2013 03:45:57 -0400 From: Rusty Russell In-Reply-To: References: <20130523085034.GA16142@redhat.com> <519F35B7.6010408@redhat.com> <20130524113542.GA7046@redhat.com> <8738tctrox.fsf@codemonkey.ws> <20130524140024.GA12024@redhat.com> <87li6yodgq.fsf@rustcorp.com.au> <87k3miq6sw.fsf@codemonkey.ws> <87r4gpkplc.fsf@rustcorp.com.au> Date: Thu, 30 May 2013 16:48:29 +0930 Message-ID: <87fvx5kkai.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] updated: kvm networking todo wiki List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: kvm , "Michael S. Tsirkin" , netdev@vger.kernel.org, Jason Wang , qemu-devel , Linux Virtualization , herbert@gondor.hengli.com.au, Anthony Liguori , Dmitry Fleytman Stefan Hajnoczi writes: > On Thu, May 30, 2013 at 7:23 AM, Rusty Russell wrote: >> On the receive side, what can we do better than readv? If we need to >> return to userspace to tell the guest that we've got a new packet, we >> don't win on latency. We might reduce syscall overhead with a >> multi-dimensional readv to read multiple packets at once? > > Sounds like recvmmsg(2). Wow... the future is here, today! Thanks, Rusty.