Many Web applications serve a significant amount of static content, which amounts to reading data off of a disk and writing the exact same data back to the response socket. This activity might appear to require relatively little CPU activity, but it's somewhat inefficient: the kernel reads the data off of disk and pushes it across the kernel-user boundary to the application, and then the application pushes it back across the kernel-user boundary to be written out to the socket. In effect, the application serves as an inefficient intermediary that gets the data from the disk file to the socket.
Each time data traverses the user-kernel boundary, it must be copied, which consumes CPU cycles and memory bandwidth. Fortunately, you can eliminate these copies through a technique called — appropriately enough — zero copy. Applications that use zero copy request that the kernel copy the data directly from the disk file to the socket, without going through the application. Zero copy greatly improves application performance and reduces the number of context switches between kernel and user mode.
The Java class libraries support zero copy on Linux and UNIX systems through the transferTo()
method injava.nio.channels.FileChannel
. You can use the transferTo()
method to transfer bytes directly from the channel on which it is invoked to another writable byte channel, without requiring data to flow through the application. This article first demonstrates the overhead incurred by simple file transfer done through traditional copy semantics, then shows how the zero-copy technique using transferTo()
achieves better performance.
Date transfer: The traditional approach
Consider the scenario of reading from a file and transferring the data to another program over the network. (This scenario describes the behavior of many server applications, including Web applications serving static content, FTP servers, mail servers, and so on.) The core of the operation is in the two calls in Listing 1 (see Download for a link to the complete sample code):
Listing 1. Copying bytes from a file to a socket
File.read(fileDesc, buf, len); Socket.send(socket, buf, len);
Although Listing 1 is conceptually simple, internally, the copy operation requires four context switches between user mode and kernel mode, and the data is copied four times before the operation is complete. Figure 1 shows how data is moved internally from the file to the socket:
Figure 1. Traditional data copying approach
Figure 2 shows the context switching:
Figure 2. Traditional context switches
The steps involved are:
- The
read()
call causes a context switch (see Figure 2) from user mode to kernel mode. Internally asys_read()
(or equivalent) is issued to read the data from the file. The first copy (see Figure 1) is performed by the direct memory access (DMA) engine, which reads file contents from the disk and stores them into a kernel address space buffer. - The requested amount of data is copied from the read buffer into the user buffer, and the
read()
call returns. The return from the call causes another context switch from kernel back to user mode. Now the data is stored in the user address space buffer. - The
send()
socket call causes a context switch from user mode to kernel mode. A third copy is performed to put the data into a kernel address space buffer again. This time, though, the data is put into a different buffer, one that is associated with the destination socket. - The
send()
system call returns, creating the fourth context switch. Independently and asynchronously, a fourth copy happens as the DMA engine passes the data from the kernel buffer to the protocol engine.
Use of the intermediate kernel buffer (rather than a direct transfer of the data into the user buffer) might seem inefficient. But intermediate kernel buffers were introduced into the process to improve performance. Using the intermediate buffer on the read side allows the kernel buffer to act as a "readahead cache" when the application hasn't asked for as much data as the kernel buffer holds. This significantly improves performance when the requested data amount is less than the kernel buffer size. The intermediate buffer on the write side allows the write to complete asynchronously.
Unfortunately, this approach itself can become a performance bottleneck if the size of the data requested is considerably larger than the kernel buffer size. The data gets copied multiple times among the disk, kernel buffer, and user buffer before it is finally delivered to the application.
Zero copy improves performance by eliminating these redundant data copies.
Data transfer: The zero-copy approach
If you re-examine the traditional scenario, you'll notice that the second and third data copies are not actually required. The application does nothing other than cache the data and transfer it back to the socket buffer. Instead, the data could be transferred directly from the read buffer to the socket buffer. The transferTo()
method lets you do exactly this. Listing 2 shows the method signature of transferTo()
:
Listing 2. The transferTo()
method
public void transferTo(long position, long count, WritableByteChannel target);
The transferTo()
method transfers data from the file channel to the given writable byte channel. Internally, it depends on the underlying operating system's support for zero copy; in UNIX and various flavors of Linux, this call is routed to the sendfile()
system call, shown in Listing 3, which transfers data from one file descriptor to another:
Listing 3. The sendfile()
system call
#include <sys/socket.h> ssize_t sendfile(int out_fd, int in_fd, off_t *offset, size_t count);
The action of the file.read()
and socket.send()
calls in Listing 1 can be replaced by a single transferTo()
call, as shown in Listing 4:
Listing 4. Using transferTo()
to copy data from a disk file to a socket
transferTo(position, count, writableChannel);
Figure 3 shows the data path when the transferTo()
method is used:
Figure 3. Data copy with transferTo()
Figure 4 shows the context switches when the transferTo()
method is used:
Figure 4. Context switching with transferTo()
The steps taken when you use transferTo()
as in Listing 4 are:
- The
transferTo()
method causes the file contents to be copied into a read buffer by the DMA engine. Then the data is copied by the kernel into the kernel buffer associated with the output socket. - The third copy happens as the DMA engine passes the data from the kernel socket buffers to the protocol engine.
This is an improvement: we've reduced the number of context switches from four to two and reduced the number of data copies from four to three (only one of which involves the CPU). But this does not yet get us to our goal of zero copy. We can further reduce the data duplication done by the kernel if the underlying network interface card supports gather operations. In Linux kernels 2.4 and later, the socket buffer descriptor was modified to accommodate this requirement. This approach not only reduces multiple context switches but also eliminates the duplicated data copies that require CPU involvement. The user-side usage still remains the same, but the intrinsics have changed:
- The
transferTo()
method causes the file contents to be copied into a kernel buffer by the DMA engine. - No data is copied into the socket buffer. Instead, only descriptors with information about the location and length of the data are appended to the socket buffer. The DMA engine passes data directly from the kernel buffer to the protocol engine, thus eliminating the remaining final CPU copy.
Figure 5 shows the data copies using transferTo()
with the gather operation:
Figure 5. Data copies when transferTo()
and gather operations are used
Building a file server
Now let's put zero copy into practice, using the same example of transferring a file between a client and a server (see Download for the sample code). TraditionalClient.java
and TraditionalServer.java
are based on the traditional copy semantics, using File.read()
andSocket.send()
. TraditionalServer.java
is a server program that listens on a particular port for the client to connect, and then reads 4K bytes of data at a time from the socket. TraditionalClient.java
connects to the server, reads (using File.read()
) 4K bytes of data from a file, and sends (using socket.send()
) the contents to the server via the socket.
Similarly, TransferToServer.java
and TransferToClient.java
perform the same function, but instead use the transferTo()
method (and in turn the sendfile()
system call) to transfer the file from server to client.
Performance comparison
We executed the sample programs on a Linux system running the 2.6 kernel and measured the run time in milliseconds for both the traditional approach and the transferTo()
approach for various sizes. Table 1 shows the results:
Table 1. Performance comparison: Traditional approach vs. zero copy
7MB | 156 | 45 |
21MB | 337 | 128 |
63MB | 843 | 387 |
98MB | 1320 | 617 |
200MB | 2124 | 1150 |
350MB | 3631 | 1762 |
700MB | 13498 | 4422 |
1GB | 18399 | 8537 |
As you can see, the transferTo()
API brings down the time approximately 65 percent compared to the traditional approach. This has the potential to increase performance significantly for applications that do a great deal of copying of data from one I/O channel to another, such as Web servers.
Summary
We have demonstrated the performance advantages of using transferTo()
compared to reading from one channel and writing the same data to another. Intermediate buffer copies — even those hidden in the kernel — can have a measurable cost. In applications that do a great deal of copying of data between channels, the zero-copy technique can offer a significant performance improvement.
Download
j-zerocopy.zip | 3KB |
相关推荐
英文论文LyraNET: A Zero-Copy TCP/IP Protocol Stack for Embedded Operating Systems的中文翻译
两万字长文从虚拟内存、I/O 缓冲区,用户态&内核态以及 I/O 模式等等知识点全面而又详尽地剖析 Linux 系统的 I/O 底层原理,分析了 Linux 传统的 I/O 模式的弊端,进而引入 Linux Zero-copy 零拷贝技术的介绍和原理...
[done]Zero-copy Receive for vhost.pdf
Design_and_implementation_of_zero-copy_data_path_for_efficient_file_transmission
java与零拷贝技术原理的一篇英文文档,图文并茂的讲解了zero 技术与java中的实现。一篇短文,值得一看
ROS2 的零拷贝技术。不可多得的学习资料。
2. 之后,CPU控制将kernel模式数据copy到user模式下 4. 最后将kernel模式下的socket buffer的数据copy到卡设备中传送 1
indices[componentId]计算出它在这个Buffer中的第个字节,然后返回结果。下再来看下componentId(int index)的实现:pr
JAVA实现的零拷贝源代码,采用SOCKET编程举例,对比了传统的SOCKET编程和实现零拷贝的SOCKET编程
在我的 4 核 8 线程 3.5Ghz i7-3770K 上测试 ASIO 最大化 UDP 发送和接收的能力。 首先,iperf 是这样运行的: A: iperf -s -u -l 65507 B: iperf -c 127.0.0.1 -u -l 65507 -b 1000G Linux 报告最大 UDP 环回吞吐...
使用pom.xml中指定的spring boot maven插件,创建Spring Boot可执行jar很简单./mvnw清洁包它会在目标文件夹(target / zerocopy-0.0.1-SNAPSHOT.jar)下生成一个重新打包的jar(可执行jar)。建立docker映像在构建...
protobuf 零拷贝网络流样本 这是使用预分配缓冲区处理流式套接字的 ZeroCopyInputStream 和 ZeroCopyOutputStream 的示例。 如果您有缓冲池或希望使用堆栈缓冲区,这将很有用。 笔记 记录代码被注释掉。...
The Need for Aynchronous, ZeroCopy Network I/OUlrich DrepperRed Hat, Inc.The ProblemNetwork hardware changed but the socket API stayed the same Transfer rates bigger (esp ...
零拷贝 零拷贝可让您避免中间缓冲区之间的冗余数据拷贝,并减少用户空间和内核空间之间的上下文切换次数。 当您的硬件(磁盘驱动器、网卡、显卡、声卡)支持DMA (直接内存访问)时,理想的零拷贝(零 CPU 拷贝)是...
BlueskyFRC是一款使用顯示卡的運算把一般24/30fps的影片轉換到60fps流暢播放既影像濾鏡,它主要支援AMD GCN1.0架構以後的顯示卡包括APU...Zero-Copy模式,配合播放器的EVR渲染器也可以把24->60fps加幀時的gpu負荷降低。
本人用的平台是xilinx, zynqMP,提供的资源是参考的源码,可以实现在一块板子上面自动播放视频。 HDMI v4l2进, HDMI DRM出 刚好在做音视频相关的工作,其他资源会在这段时间上传吧。赚点资源分去下载其他人资源。...
Efficient data transfer through zero copy 1、The read() call causes a context switch (see Figure 2) from user mode to kernel mode. Internally a sys_read() (or equivalent) is issued to read the data ...
ZSocket是Linux Zero-copy sockets的一个Golang封装库
综合分析了现有的多种零拷贝平台的实现机制及优缺点,实现了一种具有普适意义的零拷贝捕包平台(packet capture platform based on universal zero-copy,PCPUZ)。通过直接对Linux内核中套接字缓冲区的内存分配和释放...
回 0、基于 block 的传输比基于流的传输更高效、更高级的 IO 函数 zero-copy、IO 多路复用 大大提高了 Java 网络应用的可伸缩性和实用性。基于 Reactor 线程模型。 在 Reactor 模式中,事件分发器等待某个事件或者可...