aboutsummaryrefslogtreecommitdiff
path: root/sys/sys/param.h
diff options
context:
space:
mode:
authorGleb Smirnoff <glebius@FreeBSD.org>2016-01-08 20:34:57 +0000
committerGleb Smirnoff <glebius@FreeBSD.org>2016-01-08 20:34:57 +0000
commit2bab0c553588a7c2a8dd59a0f20b9b5ded528274 (patch)
treeffa24924b5fa8fa8a6a9433a56b73c595e5d33b6 /sys/sys/param.h
parent5f119e8d133b7f2bced11222d53fdca832dd84f5 (diff)
downloadsrc-2bab0c553588.tar.gz
src-2bab0c553588.zip
New sendfile(2) syscall. A joint effort of NGINX and Netflix from 2013 and
up to now. The new sendfile is the code that Netflix uses to send their multiple tens of gigabits of data per second. The new implementation features asynchronous I/O, when I/O operations are launched, but not awaited to be complete. An explanation of why such behavior is beneficial compared to old one is going to be too long for a commit message, so we will skip it here. Additional features of new syscall are extra flags, which provide an application more control over data sent. The SF_NOCACHE flag tells kernel that data shouldn't be cached after it was sent. The SF_READAHEAD() macro allows to specify readahead size in pages. The new syscalls is a drop in replacement. No modifications are required to applications. One can take nginx binary for stable/10 and run it successfully on head. Although SF_NODISKIO lost its original sense, as now sendfile doesn't block, and now means something completely different (tm), using the new sendfile the old way is absolutely safe. Celebrates: Netflix global launch! Sponsored by: Nginx, Inc. Sponsored by: Netflix Relnotes: yes
Notes
Notes: svn path=/head/; revision=293439
Diffstat (limited to 'sys/sys/param.h')
0 files changed, 0 insertions, 0 deletions