My program receives data from the socket and writes it to a file -- with the
usual read()/write() tedium.
Is there anything zero-copying like sendfile() for the socket->file direction?
In fact, sendfile's API may allow to use it in any direction, but the manual
is quite explicit, that the second (destination) argument must be socket.
recvfile()? Thanks!
-mi
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
Re: complement to sendfile()? ... My program receives data from the socket and writes it to a file -- with the ... Is there anything zero-copying like sendfile() for the socket->file direction? ... This is because network buffers can be made ... (freebsd-net)
Re: Update: Debox sendfile modifications ... > that says that sendfile() had started the reading a page. ... > a socket buffer space.... When the page had been read this flag is reset. ... (freebsd-hackers)
Re: sendfile(2) SF_NOPUSH flag proposal ... >When I turn TCP_NOPUSH on just before sendfile() then it sends the header ... The last data in the send buffer may not comprise a complete frame so ... the socket will become writable, ... As long as SO_SNDLOWAT is at least one frame smaller than SO_SNDBUF, ... (freebsd-arch)
Re: Update: Debox sendfile modifications ... > I think it can done in the following way - a socket should have flag ... > that says that sendfile() had started the reading a page. ... When the page had been read this flag is reset. ... (freebsd-hackers)
Re: Update: Debox sendfile modifications ... >> The current sendfile() implementation works with sockets only. ... >> it allows to minimize a data copy in http and ftp servers.... >> data from a socket to a file) is useless. ... To see the perfomance impact of using sendfilein http or ftp server ... (freebsd-hackers)
