From: Amit Shah <amit.shah@redhat.com>
To: qemu list <qemu-devel@nongnu.org>
Cc: Amit Shah <amit.shah@redhat.com>,
Paul Brook <paul@codesourcery.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH v4 3/5] char: unix/tcp: Add a non-blocking write handler
Date: Tue, 4 May 2010 12:47:20 +0530 [thread overview]
Message-ID: <1272957442-7832-4-git-send-email-amit.shah@redhat.com> (raw)
In-Reply-To: <1272957442-7832-3-git-send-email-amit.shah@redhat.com>
Add a non-blocking write handler that can return with -EAGAIN to the
caller and also callback when the socket becomes writable.
Non-blocking writes are only enabled for sockets that are opened in
non-blocking mode and only for callers that have registered a callback
handler for resuming writes.
Signed-off-by: Amit Shah <amit.shah@redhat.com>
---
qemu-char.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 50 insertions(+), 0 deletions(-)
diff --git a/qemu-char.c b/qemu-char.c
index 1cae1d2..476bb4e 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -2117,11 +2117,60 @@ static void tcp_chr_read(void *opaque)
}
}
+static void tcp_chr_write_unblocked(void *opaque)
+{
+ CharDriverState *chr = opaque;
+ TCPCharDriver *s = chr->opaque;
+
+ assert(chr->write_blocked && chr->chr_write_unblocked);
+
+ chr->write_blocked = false;
+ qemu_set_fd_handler2(s->fd, tcp_chr_read_poll, tcp_chr_read, NULL, chr);
+ chr->chr_write_unblocked(chr->handler_opaque);
+}
+
+static ssize_t tcp_chr_write_nb(CharDriverState *chr, const uint8_t *buf,
+ size_t len)
+{
+ TCPCharDriver *s = chr->opaque;
+ ssize_t ret;
+
+ if (!s->connected) {
+ /* XXX: indicate an error? */
+ return len;
+ }
+
+ ret = send_all(s->fd, buf, len, true);
+ if (ret == -EAGAIN) {
+ chr->write_blocked = true;
+ qemu_set_fd_handler2(s->fd, tcp_chr_read_poll,
+ tcp_chr_read, tcp_chr_write_unblocked, chr);
+ }
+ return ret;
+}
+
static void tcp_chr_connect(void *opaque)
{
CharDriverState *chr = opaque;
TCPCharDriver *s = chr->opaque;
+ IOHandler *write_cb;
+ int flags;
+ bool nonblock;
+
+ flags = fcntl(s->fd, F_GETFL);
+ if (flags == -1) {
+ flags = 0;
+ }
+ nonblock = flags & O_NONBLOCK;
+
+ write_cb = NULL;
+ chr->nonblock = false;
+ if (nonblock && chr->chr_write_unblocked) {
+ write_cb = chr->chr_write_unblocked;
+ chr->nonblock = true;
+ }
+ chr->write_blocked = false;
s->connected = 1;
qemu_set_fd_handler2(s->fd, tcp_chr_read_poll,
tcp_chr_read, NULL, chr);
@@ -2254,6 +2303,7 @@ static CharDriverState *qemu_chr_open_socket(QemuOpts *opts)
chr->opaque = s;
chr->chr_write = tcp_chr_write;
+ chr->chr_write_nb = tcp_chr_write_nb;
chr->chr_close = tcp_chr_close;
chr->get_msgfd = tcp_get_msgfd;
--
1.6.2.5
next prev parent reply other threads:[~2010-05-04 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 7:17 [Qemu-devel] [PATCH v4 0/5] char: non-blocking writes, virtio-console flow control Amit Shah
2010-05-04 7:17 ` [Qemu-devel] [PATCH v4 1/5] char: Let writers know how much data was written in case of errors Amit Shah
2010-05-04 7:17 ` [Qemu-devel] [PATCH v4 2/5] char: Add qemu_chr_write_nb() for nonblocking writes Amit Shah
2010-05-04 7:17 ` Amit Shah [this message]
2010-05-04 7:17 ` [Qemu-devel] [PATCH v4 4/5] virtio-console: Factor out common init between console and generic ports Amit Shah
2010-05-04 7:17 ` [Qemu-devel] [PATCH v4 5/5] virtio-console: Throttle virtio-serial-bus if we can't consume any more guest data Amit Shah
2010-05-04 7:43 ` [Qemu-devel] Re: [PATCH v4 3/5] char: unix/tcp: Add a non-blocking write handler Gerd Hoffmann
2010-05-04 7:56 ` Amit Shah
2010-05-04 8:13 ` Gerd Hoffmann
2010-05-04 7:38 ` [Qemu-devel] Re: [PATCH v4 2/5] char: Add qemu_chr_write_nb() for nonblocking writes Gerd Hoffmann
2010-05-04 7:58 ` Amit Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1272957442-7832-4-git-send-email-amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=kraxel@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).