Lines Matching full:userspace

7 OrangeFS is an LGPL userspace scale-out parallel storage system. It is ideal
22   * Userspace implementation is easy to install and maintain
87 Userspace Filesystem Source
230 Protocol between Kernel Module and Userspace
234 We'll just refer to the user space part of Orangefs as "userspace"
235 from here on out. Orangefs descends from PVFS, and userspace code
236 still uses PVFS for function and variable names. Userspace typedefs
240 correspond to userspace structures are not typedefed.
242 The kernel module implements a pseudo device that userspace
243 can read from and write to. Userspace can also manipulate the
249 At startup userspace allocates two page-size-aligned (posix_memalign)
313 needs to communicate with userspace. Part of the op contains the "upcall"
314 which expresses the request to userspace. Part of the op eventually
339 When some arbitrary userspace program needs to perform a
347 function through a wait queue. Userspace is polling the pseudo-device
353 the filled-out upcall struct are copy_to_user'ed back to userspace.
361 When userspace has assembled the response to the upcall, it
374 userspace. The client-core is a daemon. The client-core has an
382 if the client-core stays dead too long, the arbitrary userspace processes
392     memory buffers. The readdir buffer is only available to userspace.
394     a readdir op. Userspace deposits the results into the indexed partition
399     both userspace and the kernel module. The kernel module obtains an
402     directly by userspace. Userspace deposits the results of read
473 Userspace uses writev() on /dev/pvfs2-req to pass responses to the requests
515 requests to userspace. We keep object inode attributes up-to-date with
541 dentries is to always obtain the needed information from userspace - at
543 from a dentry is cheap, obtaining it from userspace is relatively expensive,