From f749998939e564d8b8363bd6148b7a067d6bc9e3 Mon Sep 17 00:00:00 2001 From: pbrook Date: Sun, 28 Jan 2007 00:10:01 +0000 Subject: Add nodelay option for TCP character devices. git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@2362 c046a42c-6fe2-441c-8c8c-71466251a162 --- qemu-doc.texi | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'qemu-doc.texi') diff --git a/qemu-doc.texi b/qemu-doc.texi index 11cd82c..4b9c5f4 100644 --- a/qemu-doc.texi +++ b/qemu-doc.texi @@ -576,13 +576,14 @@ localhost 5555 @end table -@item tcp:[host]:port[,server][,nowait] +@item tcp:[host]:port[,server][,nowait][,nodelay] The TCP Net Console has two modes of operation. It can send the serial I/O to a location or wait for a connection from a location. By default the TCP Net Console is sent to @var{host} at the @var{port}. If you use the @var{server} option QEMU will wait for a client socket application to connect to the port before continuing, unless the @code{nowait} -option was specified. If @var{host} is omitted, 0.0.0.0 is assumed. Only +option was specified. The @code{nodelay} option disables the Nagle buffering +algoritm. If @var{host} is omitted, 0.0.0.0 is assumed. Only one TCP connection at a time is accepted. You can use @code{telnet} to connect to the corresponding character device. @table @code @@ -594,7 +595,7 @@ connect to the corresponding character device. -serial tcp:192.168.0.100:4444,server,nowait @end table -@item telnet:host:port[,server][,nowait] +@item telnet:host:port[,server][,nowait][,nodelay] The telnet protocol is used instead of raw tcp sockets. The options work the same as if you had specified @code{-serial tcp}. The difference is that the port acts like a telnet server or client using -- cgit v1.1