Lines Matching +full:9 +full:a

3  * include/net/9p/9p.h
5  * 9P protocol definitions.
18  * @P9_DEBUG_9P: 9P protocol tracing
43 	P9_DEBUG_FID =		(1<<9),
62  * enum p9_msg_t - 9P message types
64  * @P9_RLERROR: response for any failed request for 9P2000.L
69  * @P9_TMKNOD: create a special file object request
70  * @P9_RMKNOD: create a special file object response
71  * @P9_TLCREATE: prepare a handle for I/O on an new file for 9P2000.L
72  * @P9_RLCREATE: response with file access information for 9P2000.L
75  * @P9_TMKDIR: create a directory request
76  * @P9_RMKDIR: create a directory response
85  * @P9_TFLUSH: request to abort a previous request
87  * @P9_TWALK: descend a directory hierarchy
89  * @P9_TOPEN: prepare a handle for I/O on an existing file
91  * @P9_TCREATE: prepare a handle for I/O on a new file
93  * @P9_TREAD: request to transfer data from a file or directory
95  * @P9_TWRITE: reuqest to transfer data to a file
97  * @P9_TCLUNK: forget about a handle to an entity within the file system
106  * There are 14 basic operations in 9P2000, paired as
187  * enum p9_open_mode_t - 9P open modes
196  * @P9_OEXCL: only create a file, do not open it
198  * 9P open modes differ slightly from Posix standard modes.
221  * enum p9_perm_t - 9P permissions
228  * @P9_DMSYMLINK: mode bit for symbolic links (9P2000.u)
229  * @P9_DMLINK: mode bit for hard-link (9P2000.u)
230  * @P9_DMDEVICE: mode bit for device files (9P2000.u)
231  * @P9_DMNAMEDPIPE: mode bit for named pipe (9P2000.u)
232  * @P9_DMSOCKET: mode bit for socket (9P2000.u)
233  * @P9_DMSETUID: mode bit for setuid (9P2000.u)
234  * @P9_DMSETGID: mode bit for setgid (9P2000.u)
235  * @P9_DMSETVTX: mode bit for sticky bit (9P2000.u)
237  * 9P permissions differ slightly from Posix standard modes.
248 /* 9P2000.u extensions */
259 /* 9p2000.L open flags */
280 /* 9p2000.L at flags */
283 /* 9p2000.L lock type */
296  * @P9_QTSYMLINK: symbolic links (9P2000.u)
297  * @P9_QTLINK: hard-link (9P2000.u)
300  * QID types are a subset of permissions - they are primarily
301  * used to differentiate semantics for a file system entity via
302  * a jump-table.  Their value is also the most significant 16 bits
319 /* 9P Magic Numbers */
340  * @path: 64-bit per-server-unique ID for a file system element
342  * qids are identifiers used by 9P servers to track file system
344  * on the entity (ie. read means something different on a directory than
345  * on a file).  The path provides a server unique index for an entity
347  * every time a file is modified and can be used to maintain cache
365  * @type: the type of the server (equivalent to a major number)
366  * @dev: the sub-type of the server (equivalent to a minor number)
368  * @mode: Plan 9 format permissions of type &p9_perm_t
377  * @n_uid: numeric user id of owner (part of 9p2000.u extension)
378  * @n_gid: numeric group id (part of 9p2000.u extension)
379  * @n_muid: numeric user id of laster modifier (part of 9p2000.u extension)
397 	char *extension;	/* 9p2000.u extensions */
398 	kuid_t n_uid;		/* 9p2000.u extensions */
399 	kgid_t n_gid;		/* 9p2000.u extensions */
400 	kuid_t n_muid;		/* 9p2000.u extensions */
534  * &p9_fcall represents the structure for all 9P RPC