From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MOZnx-0007Jf-Oo for qemu-devel@nongnu.org; Wed, 08 Jul 2009 12:15:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOZns-0007Ac-W0 for qemu-devel@nongnu.org; Wed, 08 Jul 2009 12:15:33 -0400 Received: from [199.232.76.173] (port=42355 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOZns-0007AJ-OV for qemu-devel@nongnu.org; Wed, 08 Jul 2009 12:15:28 -0400 Received: from mx20.gnu.org ([199.232.41.8]:16791) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MOZns-0000ie-5s for qemu-devel@nongnu.org; Wed, 08 Jul 2009 12:15:28 -0400 Received: from mx2.redhat.com ([66.187.237.31]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MOZnr-0004PU-Bd for qemu-devel@nongnu.org; Wed, 08 Jul 2009 12:15:27 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n68GFPnr025756 for ; Wed, 8 Jul 2009 12:15:25 -0400 Message-ID: <4A54C6B4.8010504@redhat.com> Date: Wed, 08 Jul 2009 19:17:56 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 2/5] Add SCM_RIGHTS support to unix socket character devices References: <1247064963.3270.63.camel@blaa> <1247065048-15706-1-git-send-email-markmc@redhat.com> <1247065048-15706-2-git-send-email-markmc@redhat.com> <4A54BA4D.4040809@redhat.com> <1247069043.3270.83.camel@blaa> In-Reply-To: <1247069043.3270.83.camel@blaa> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark McLoughlin Cc: qemu-devel@nongnu.org On 07/08/2009 07:04 PM, Mark McLoughlin wrote: > >> and multiple messages can arrive. I think you need to queue fds here >> in case the client sends two getfd commands back-to-back and does >> buffering. >> > > it doesn't look to me like the current monitor code can handle multiple > commands in the one message. > How does qemu have any control over the division of messages and packets? I can send commands byte by byte or queue them up and send a gigabyte's worth in one go (when we have -monitor ib:blah). -- error compiling committee.c: too many arguments to function