Lines Matching refs:and

7 POHMELFS first began as a network filesystem with coherent local data and
11  * Locally coherent cache for data and metadata with (potentially) byte-range locks.
13 	is very simple and does not use byte-ranges, although they are sent in
15  * Completely async processing of all events except creation of hard and symbolic
16 	links, and rename events.
17 	Object creation and data reading and writing are processed asynchronously.
19 	Ability to create long paths to objects and remove arbitrarily huge
23  * Fast and scalable multithreaded userspace server. Being in userspace it works
24 	with any underlying filesystem and still is much faster than async in-kernel NFS one.
26 	automatically reconnects to second and so on).
30  * Write requests are replicated to multiple servers and completed only when all of them are acked.
31  * Ability to add and/or remove servers from the working set at run-time.
32  * Strong authentification and possible data encryption in network channel.
38 can contain creation and data writing commands). Transactions are committed by all the servers
39 to which they are sent and, in case of failures, are eventually resent or dropped with an error.
43 possible to detach replies from requests and, if the command requires data to be received, the
45 servers and async threads will pick up replies in parallel, find appropriate transactions in the
46 system and put the data where it belongs (like the page or inode cache).
48 The main feature of POHMELFS is writeback data and the metadata cache.
49 Only a few non-performance critical operations use the write-through cache and
50 are synchronous: hard and symbolic link creation, and object rename. Creation,
51 removal of objects and data writing are asynchronous and are sent to
55 workloads and can fully utilize the bandwidth to the servers when doing bulk
58 POHMELFS clients operate with a working set of servers and are capable of balancing read-only
62 are connected with write permission turned on. IO priority and permissions can be changed in
65 POHMELFS is capable of full data channel encryption and/or strong crypto hashing.
66 One can select any kernel supported cipher, encryption mode, hash type and operation mode
68 is checked during mount time and, if the server does not support it, appropriate capabilities
71 crypto operations and send the resulting data to server or submit it up the stack. This number