marc 98/03/07 20:39:16
Modified: docs page_io
Log:
no snow.
Revision Changes Path
1.6 +18 -1 apache-2.0/docs/page_io
Index: page_io
===================================================================
RCS file: /export/home/cvs/apache-2.0/docs/page_io,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- page_io 1998/03/08 04:22:39 1.5
+++ page_io 1998/03/08 04:39:14 1.6
@@ -96,7 +96,7 @@
descriptor across the network. This is probably the single best way
to do static content on systems that support it.
-HPUX:
+HPUX: (11.0 and on)
ssize_t sendfile(int s, int fd, off_t offset, size_t nbytes,
const struct iovec *hdtrl, int flags);
@@ -140,3 +140,20 @@
TransmitFile. If not, you are just limited (eg. byte
ranges) in what you can use it for.
+ Also note that TransmitFile can specify TF_REUSE_SOCKET, so that
+ after use the same socket handle can be passed to AcceptEx.
+ Obviously only good where we don't have a persistent connection
+ to worry about.
+
+----
+
+Note that all this is shot to bloody hell by HTTP-NG's multiplexing.
+If fragment sizes are big enough, it could still be worthwhile to
+do copy avoidence. It also causes performance issues because of
+its credit system that limits how much you can write in a single
+chunk.
+
+Don't tell me that if HTTP-NG becomes popular we will seen vendors
+embedding SMUX (or whatever multiplexing is used) in the kernel to
+get around this stuff. There we go, Apache with a loadable kernel
+module.
