From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=38598 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PNmQB-0001m2-56 for qemu-devel@nongnu.org; Wed, 01 Dec 2010 08:08:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PNmQA-00027Q-6F for qemu-devel@nongnu.org; Wed, 01 Dec 2010 08:08:30 -0500 Received: from mail.codesourcery.com ([38.113.113.100]:41108) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PNmQ9-00026w-Sw for qemu-devel@nongnu.org; Wed, 01 Dec 2010 08:08:30 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH v8 7/7] virtio-console: Enable port throttling when chardev is slow to consume data Date: Wed, 1 Dec 2010 13:08:26 +0000 References: <201012011159.35947.paul@codesourcery.com> <20101201121256.GD2962@amit-x200.redhat.com> In-Reply-To: <20101201121256.GD2962@amit-x200.redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201012011308.26315.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: Juan Quintela , qemu-devel@nongnu.org, Gerd Hoffmann > On (Wed) Dec 01 2010 [11:59:35], Paul Brook wrote: > > > > > - qemu_chr_write(vcon->chr, buf, len); > > > > > + ret = qemu_chr_write(vcon->chr, buf, len); > > > > > + if (ret == -EAGAIN) { > > > > > + virtio_serial_throttle_port(port, true); > > > > > + } > > > > > > > > > > } > > > > > > > > This looks wrong. It will loose data in the case of a partial write > > > > (i.e. ret < len) > > > > > > That doesn't happen currently (qemu_chr_write doesn't return a value > > > > 0 but < len). > > > > > > I had code in there to handle it, but that would change behaviour for > > > current users of qemu_chr_write(), which is a risk. > > > > Doesn't that make the code almost completely pointless? > > Not really -- I did have code for partial writes, but removed it before > this submission (had it in previous versions). > > The (new) do_send loop: > > len = len1; > while (len > 0) { > ret = write(fd, buf, len); > if (ret < 0) { > if (errno == EAGAIN && nonblock) { > return -EAGAIN; > } > if (errno != EINTR && errno != EAGAIN) { > return -1; > } > } else if (ret == 0) { > break; > } else { > buf += ret; > len -= ret; > } > } > > when there's a partial write, it tries to do a write again, which will > fail with -EAGAIN. Doesn't that cause the first partial chunk to be incorrectly transmitted twice? You may only return EAGAIN if no data was transmitted. Paul