On a side note, I think that the above will block on the first splice_all when the file is large enough due to the pipe filling up(?), so I also have a version of the code that forks to read and write from the pipe at the same time, but it has the same error as this version and is harder to read.ĮDIT: My kernel version is 2.6.22.18-co-0.7.3 (running coLinux on XP. Static void transfer(int from, int to, long long bytes) for Fiber Optic Splice Closures, Telcordia Technologies, Issue 2, July 2008. static void splice_all(int from, int to, long long bytes) It's based heavily on the Wikipedia example for splice. I'm including the code below (minus error handling code) in the hopes that I've just done something wrong. The man page states that EINVAL is set when neither descriptor is a pipe (not the case), an offset is passed for a stream that can't seek (no offsets passed), or the filesystem doesn't support splicing, which leads me to my question: does this mean that TCP can splice from a pipe, but not to? If your video clips are on a smartphone, youll need to transfer them to your computer before you can splice. It transfers up to lenbytes of data from the file descriptor fdinto the file descriptor fdout, where one of the file descriptors must refer to a pipe. 1.Transfer your video clips to your computer. The code I wrote with splice works perfectly when reading from stdin (redirected file) and writing to the TCP socket, but fails immediately with splice setting errno to EINVAL when reading from socket and writing to stdout. splice() moves data between two file descriptors without copying between kernel address space and user address space. I originally used read/write and the program worked correctly, but then I learned about splice and wanted to give it a try. The program reads a file from a socket and writes it to file (or vice versa). I've been writing a little program for fun that transfers files over TCP in C on Linux.
0 kommentar(er)
