Function report |
Source Code:fs\splice.c |
Create Date:2022-07-28 20:11:28 |
Last Modify:2020-03-12 14:18:49 | Copyright©Brick |
home page | Tree |
Annotation kernel can get tool activity | Download SCCT | Chinese |
Name:vmsplice splices a user address range into a pipe. It can be thought of* as splice-from-memory, where the regular splice is splice-from-file (or* to file). In both cases the output is a pipe, naturally.
Proto:static long vmsplice_to_pipe(struct file *file, struct iov_iter *iter, unsigned int flags)
Type:long
Parameter:
Type | Parameter | Name |
---|---|---|
struct file * | file | |
struct iov_iter * | iter | |
unsigned int | flags |
1310 | ret = 0 |
1311 | buf_flag = 0 |
1313 | If flags & pages passed in are a gift Then buf_flag = page is a gift |
1316 | pipe = After the inode slimming patch, i_pipe/i_bdev/i_cdev share the same* location, so checking ->i_pipe is not enough to verify that this is a* pipe. |
1321 | ret = wait_for_space(pipe, flags) |
1324 | pipe_unlock(pipe) |
1325 | If ret > 0 Then wakeup_pipe_readers(pipe) |
1327 | Return ret |
Name | Describe |
---|---|
do_vmsplice | Note that vmsplice only really supports true splicing _from_ user memory* to a pipe, not the other way around. Splicing from user memory is a simple* operation that can be supported without any funky alignment restrictions* or nasty vm tricks |
Source code conversion tool public plug-in interface | X |
---|---|
Support c/c++/esqlc/java Oracle/Informix/Mysql Plug-in can realize: logical Report Code generation and batch code conversion |