1splice(2) Linux Programmer's Manual splice(2)
2
6 splice - splice data to/from a pipe
7
9 #define _GNU_SOURCE
10 #include <fcntl.h>
11 long splice(int fd_in, off_t *off_in, int fd_out,
13 off_t *off_out, size_t len, unsigned int flags);
14
16 splice() moves data between two file descriptors without copying
17 between kernel address space and user address space. It transfers up
18 to len bytes of data from the file descriptor fd_in to the file
19 descriptor fd_out, where one of the descriptors must refer to a pipe.
20 If fd_in refers to a pipe, then off_in must be NULL. If fd_in does not
22 refer to a pipe and off_in is NULL, then bytes are read from fd_in
23 starting from the current file offset, and the current file offset is
24 adjusted appropriately. If fd_in does not refer to a pipe and off_in
25 is not NULL, then off_in must point to a buffer which specifies the
26 starting offset from which bytes will be read from fd_in; in this case,
27 the current file offset of fd_in is not changed. Analogous statements
28 apply for out_fd and off_out.
29 The flags argument is a bit mask that is composed by ORing together
31 zero or more of the following values:
32 SPLICE_F_MOVE Attempt to move pages instead of copying. This is
34 only a hint to the kernel: pages may still be copied
35 if the kernel cannot move the pages from the pipe,
36 or if the pipe buffers don't refer to full pages.
37 SPLICE_F_NONBLOCK Do not block on I/O. This makes the splice pipe
39 operations non-blocking, but splice() may neverthe‐
40 less block because the file descriptors that are
41 spliced to/from may block (unless they have the
42 O_NONBLOCK flag set).
43 SPLICE_F_MORE More data will be coming in a subsequent splice.
45 This is a helpful hint when the fd_out refers to a
46 socket (see also the description of MSG_MORE in
47 send(2), and the description of TCP_CORK in tcp(7))
48 SPLICE_F_GIFT Unused for splice(); see vmsplice(2).
50
52 Upon successful completion, splice() returns the number of bytes
53 spliced to or from the pipe. A return value of 0 means that there was
54 no data to transfer, and it would not make sense to block, because
55 there are no writers connected to the write end of the pipe referred to
56 by fd_in.
57 On error, splice() returns -1 and errno is set to indicate the error.
59
61 EBADF One or both file descriptors are not valid, or do not have
62 proper read-write mode.
63 EINVAL Target file system doesn't support splicing; neither of the
65 descriptors refers to a pipe; or offset given for non-seekable
66 device.
67 ENOMEM Out of memory.
69 ESPIPE Either off_in or off_out was not NULL, but the corresponding
71 file descriptor refers to a pipe.
72
74 The splice(2) system call first appeared in Linux-2.6.17.
75
77 The three system calls splice(2), vmsplice(2), and tee(2)), provide
78 userspace programs with full control over an arbitrary kernel buffer,
79 implemented within the kernel using the same type of buffer that is
80 used for a pipe. In overview, these system calls perform the following
81 tasks:
82 splice() moves data from the buffer to an arbitrary file descriptor,
84 or vice versa, or from one buffer to another.
85 tee() "copies" the data from one buffer to another.
87 vmsplice() "copies" data from user space into the buffer.
89 Though we talk of copying, actual copies are generally avoided. The
91 kernel does this by implementing a pipe buffer as a set of reference-
92 counted pointers to pages of kernel memory. The kernel creates
93 "copies" of pages in a buffer by creating new pointers (for the output
94 buffer) referring to the pages, and increasing the reference counts for
95 the pages: only pointers are copied, not the pages of the buffer.
96
98 See tee(2).
99
101 This system call is Linux specific.
102
104 sendfile(2), splice(2), tee(2), feature_test_macros(7)
105Linux 2.6.17 2006-04-28 splice(2)