From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52887 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PJ2cd-0008VS-Ne for qemu-devel@nongnu.org; Thu, 18 Nov 2010 06:25:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PJ2cc-0006yI-Q9 for qemu-devel@nongnu.org; Thu, 18 Nov 2010 06:25:47 -0500 Received: from mx1.redhat.com ([209.132.183.28]:21234) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PJ2cc-0006yD-J8 for qemu-devel@nongnu.org; Thu, 18 Nov 2010 06:25:46 -0500 Message-ID: <4CE50D36.80404@redhat.com> Date: Thu, 18 Nov 2010 12:25:42 +0100 From: Jes Sorensen MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC][PATCH v3 10/21] virtproxy: add handler for data packets References: <1289870175-14880-1-git-send-email-mdroth@linux.vnet.ibm.com> <1289870175-14880-11-git-send-email-mdroth@linux.vnet.ibm.com> In-Reply-To: <1289870175-14880-11-git-send-email-mdroth@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Roth Cc: agl@linux.vnet.ibm.com, abeekhof@redhat.com, qemu-devel@nongnu.org, aliguori@linux.vnet.ibm.com, ryanh@us.ibm.com, amit.shah@redhat.com On 11/16/10 02:16, Michael Roth wrote: > + if (pkt->type == VP_PKT_CLIENT) { > + TRACE("recieved client packet, client fd: %d, server fd: %d", > + pkt->payload.proxied.client_fd, pkt->payload.proxied.server_fd); > + fd = pkt->payload.proxied.server_fd; > + } else if (pkt->type == VP_PKT_SERVER) { > + TRACE("recieved server packet, client fd: %d, server fd: %d", > + pkt->payload.proxied.client_fd, pkt->payload.proxied.server_fd); > + fd = pkt->payload.proxied.client_fd; > + } else { > + TRACE("unknown packet type"); > + return -1; > + } -1 isn't a very friendly error value to pass up the stack. > + /* TODO: proxied in non-blocking mode can causes us to spin here > + * for slow servers/clients. need to use write()'s and maintain > + * a per-conn write queue that we clear out before sending any > + * more data to the fd > + */ > + ret = vp_send_all(fd, (void *)pkt->payload.proxied.data, > + pkt->payload.proxied.bytes); > + if (ret == -1) { > + LOG("error sending data over channel"); > + return -1; > + } else if (ret != pkt->payload.proxied.bytes) { > + TRACE("buffer full?"); > + return -1; > + } Again here, please pass the error codes up the stack so we can later handle them appropriately. Cheers, Jes