Splice (system Call)

splice is a Linux-specific system call that moves data between a file descriptor and a pipe without a round trip to user space. The related system call vmsplice moves or copies data between a pipe and user space. Ideally, splice and vmsplice work by remapping pages and do not actually copy any data, which may improve I/O performance. As linear addresses do not necessarily correspond to contiguous physical addresses, this may not be possible in all cases and on all hardware combinations.


With splice, one can move data from one file descriptor to another without incurring any copies from user space into kernel space, which is usually required to enforce system security and also to keep a simple interface for processes to read and write to files. splice works by using the pipe buffer. A pipe buffer is an in-kernel memory buffer that is opaque to the user space process. A user process can splice the contents of a source file into this pipe buffer, then splice the pipe buffer into the destination file, all without moving any data through userspace.

Linus Torvalds described splice in a 2006 email, which was included in a KernelTrap article.[1]


The Linux splice implementation borrows some ideas from an original proposal by Larry McVoy in 1998.[2] The splice system calls first appeared in Linux kernel version 2.6.17 and were written by Jens Axboe.


 ssize_t splice(int fd_in, loff_t *off_in, int fd_out, loff_t *off_out, size_t len, unsigned int flags);

Some constants that are of interest are:

/* Splice flags (not laid down in stone yet). */
#define SPLICE_F_MOVE           0x01
#define SPLICE_F_NONBLOCK       0x02
#define SPLICE_F_MORE           0x04
#define SPLICE_F_GIFT           0x08


This is an example of splice in action:

/* This example is wrong. A pipe is a kernel buffer of fixed size,
 * so if you try to splice a big enough file directly into it,
 * you're going to either be blocked indefinitely or get an error.
 * You should splice, in a loop, a chunk of data which does not exceed
 * the dimension of the pipe buffer in each iteration.

/* Transfer from disk to a log. */
int log_blocks (struct log_handle * handle, int fd, loff_t offset, size_t size)
    int filedes [2];
    int ret;
    size_t to_write = size;
    ret = pipe (filedes);
    if (ret < 0)
        goto out;
    /* splice the file into the pipe (data in kernel memory). */
    while (to_write > 0) {
        ret = splice (fd, &offset, filedes [1], NULL, to_write,
                SPLICE_F_MORE | SPLICE_F_MOVE);
        if (ret < 0)
            goto pipe;
            to_write -= ret;
    to_write = size;
    /* splice the data in the pipe (in kernel memory) into the file. */
    while (to_write > 0) {
        ret = splice (filedes [0], NULL, handle->fd,
                &(handle->fd_offset), to_write,
                SPLICE_F_MORE | SPLICE_F_MOVE);
        if (ret < 0)
            goto pipe;
            to_write -= ret;

    close (filedes [0]);
    close (filedes [1]);
    if (ret < 0)
        return -errno;
    return 0;

Complementary system calls

splice is one of three system calls that complete the splice architecture. vmsplice can map an application data area into a pipe (or vice versa), thus allowing transfers between pipes and user memory where sys_splice transfers between a file descriptor and a pipe. tee is the last part of the trilogy. It duplicates one pipe to another, enabling forks in the way applications are connected with pipes.


When using splice with sockets, the network controller (NIC) must support DMA.

When the NIC does not support DMA then splice will not deliver a large performance improvement. The reason for this is that each page of the pipe will just fill up to frame size (1460 bytes of the available 4096 bytes per page).

Not all filesystem types support splice. Also, AF_UNIX sockets do not support splice.

See also


  1. ^ "Linux: Explaining splice and tee". kerneltrap.org. 2006-04-21. Archived from the original on 2013-05-21. Retrieved .
  2. ^ "Archived copy". Archived from the original on 2016-03-04. Retrieved .

External links

  This article uses material from the Wikipedia page available here. It is released under the Creative Commons Attribution-Share-Alike License 3.0.



Connect with defaultLogic
What We've Done
Led Digital Marketing Efforts of Top 500 e-Retailers.
Worked with Top Brands at Leading Agencies.
Successfully Managed Over $50 million in Digital Ad Spend.
Developed Strategies and Processes that Enabled Brands to Grow During an Economic Downturn.
Taught Advanced Internet Marketing Strategies at the graduate level.

Manage research, learning and skills at defaultlogic.com. Create an account using LinkedIn to manage and organize your omni-channel knowledge. defaultlogic.com is like a shopping cart for information -- helping you to save, discuss and share.

  Contact Us