/** * Maximum size of read requests. A value of zero indicates no * limit. However, even if the filesystem does not specify a * limit, the maximum size of read requests will still be * limited by by the kernel. * * NOTE: For the time being, the maximum size of read requests© XXX Page 11 of 33 * must be set both here *and* passed to fuse_session_new() * using the ``-o max_read=`` mount pending "background" requests. A * background request is any type of request for which the * total number is not limited by other means. As of kernel * 4.8, only two types of requests fall into this category:

the two. l Nebdclient: Forward the requests from QEMU and curve-NBD to the specified NEBDServer through Unix Domain sockets. l Nebdserver: Accepts requests from NEBDClient and calls Curve Client Client for corresponding processing. it can receive requests from different NEBDClients.3. Through the above splitting, NebdClient replaces Curve Client and directly interfaces with upper services. There There is no logical processing in NEBDClient, it just proxy requests and has limited retries, which ensuring that NEBDClient needs no change. To upgrade curve-client, you only need to restart the

may thus be omitted by the filesystem. When writeback caching is enabled, the kernel may send read requests even for files opened with O_WRONLY. The filesystem should be prepared to handle this. When writeback match the *fh* value that would have been sent with the corresponding individual write requests if write caching had been disabled. */ unsigned int writepage : 1; /** Can be filled in by open

unlink, rmdir or (when * overwriting an existing file) rename. Filesystems must handle * such requests properly and it is recommended to defer removal * of the inode until the lookup count reaches