motorhead/qemu
1
0
Fork 0
mirror of https://github.com/Motorhead1991/qemu.git synced 2025-08-04 08:13:54 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

virtiofsd: Remove unused enum fuse_buf_copy_flags

Browse source 
Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
This commit is contained in:
Xiao Yang 2020-01-22 10:40:08 +08:00 • committed by Dr. David Alan Gilbert
parent 64c6f408a2
commit 8c3fe75e03
5 changed files with 13 additions and 92 deletions
Download patch file Download diff file Expand all files Collapse all files

35
tools/virtiofsd/fuse_lowlevel.h
View file

@ -1363,33 +1363,6 @@ int fuse_reply_buf(fuse_req_t req, const char *buf, size_t size);
/**
* Reply with data copied/moved from buffer(s)
*
* Zero copy data transfer ("splicing") will be used under
* the following circumstances:
*
* 1. FUSE_CAP_SPLICE_WRITE is set in fuse_conn_info.want, and
* 2. the kernel supports splicing from the fuse device
* (FUSE_CAP_SPLICE_WRITE is set in fuse_conn_info.capable), and
* 3. *flags* does not contain FUSE_BUF_NO_SPLICE
* 4. The amount of data that is provided in file-descriptor backed
* buffers (i.e., buffers for which bufv[n].flags == FUSE_BUF_FD)
* is at least twice the page size.
*
* In order for SPLICE_F_MOVE to be used, the following additional
* conditions have to be fulfilled:
*
* 1. FUSE_CAP_SPLICE_MOVE is set in fuse_conn_info.want, and
* 2. the kernel supports it (i.e, FUSE_CAP_SPLICE_MOVE is set in
fuse_conn_info.capable), and
* 3. *flags* contains FUSE_BUF_SPLICE_MOVE
*
* Note that, if splice is used, the data is actually spliced twice:
* once into a temporary pipe (to prepend header data), and then again
* into the kernel. If some of the provided buffers are memory-backed,
* the data in them is copied in step one and spliced in step two.
*
* The FUSE_BUF_SPLICE_FORCE_SPLICE and FUSE_BUF_SPLICE_NONBLOCK flags
* are silently ignored.
*
* Possible requests:
* read, readdir, getxattr, listxattr
*
@ -1400,11 +1373,9 @@ int fuse_reply_buf(fuse_req_t req, const char *buf, size_t size);
*
* @param req request handle
* @param bufv buffer vector
* @param flags flags controlling the copy
* @return zero for success, -errno for failure to send reply
*/
int fuse_reply_data(fuse_req_t req, struct fuse_bufvec *bufv,
enum fuse_buf_copy_flags flags);
int fuse_reply_data(fuse_req_t req, struct fuse_bufvec *bufv);
/**
* Reply with data vector
@ -1705,12 +1676,10 @@ int fuse_lowlevel_notify_delete(struct fuse_session *se, fuse_ino_t parent,
* @param ino the inode number
* @param offset the starting offset into the file to store to
* @param bufv buffer vector
* @param flags flags controlling the copy
* @return zero for success, -errno for failure
*/
int fuse_lowlevel_notify_store(struct fuse_session *se, fuse_ino_t ino,
off_t offset, struct fuse_bufvec *bufv,
enum fuse_buf_copy_flags flags);
off_t offset, struct fuse_bufvec *bufv);
/*
* Utility functions