linux-toradex.git/include/net/9p, branch v2.6.39-rc5

net/9p: nwname should be an unsigned int

2011-04-15T20:26:15+00:00

Signed-off-by: Harsh Prateek Bora 
Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric VAn Hensbergen

9p: revert tsyncfs related changes

2011-04-15T20:26:14+00:00

Now that we use write_inode to flush server
cache related to fid, we don't need tsyncfs either fort dotl or dotu
protocols. For dotu this helps to do a more efficient server flush.

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

Fix common misspellings

2011-03-31T14:26:23+00:00

Fixes generated by 'codespell' and manually reviewed.

Signed-off-by: Lucas De Marchi

net/9p: Implement syncfs 9P operation

2011-03-15T14:57:38+00:00

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

[net/9p] Small non-IO PDUs for zero-copy supporting transports.

2011-03-15T14:57:36+00:00

If a transport prefers payload to be sent separate from the PDU
(P9_TRANS_PREF_PAYLOAD_SEP), there is no need to allocate msize
PDU buffers(struct p9_fcall).

This patch allocates only upto 4k buffers for this kind of transports
and there won't be any change to the legacy transports.

Hence, this patch on top of zero copy changes allows user to
specify higher msizes through the mount option
without hogging the kernel heap.

Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

[net/9p] Add preferences to transport layer.

2011-03-15T14:57:35+00:00

This patch adds preferences field to the p9_trans_module.
Through this, now transport layer can express its preference about the
payload. i.e if payload neds to be part of the PDU or it prefers it
to be sent sepearetly so that the transport layer can handle it in
a better way.

Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

[net/9p] Preparation and helper functions for zero copy

2011-03-15T14:57:34+00:00

This patch prepares p9_fcall structure for zero copy. Added
fields send the payload buffer information to the transport layer.
In addition it adds a 'private' field for the transport layer to
store mapped/pinned page information so that it can be freed/unpinned
during req_done.

This patch also creates trans_common.[ch] to house helper functions.
It adds the following helper functions.

p9_release_req_pages - Release pages after the transaction.
p9_nr_pages - Return number of pages needed to accomodate the payload.
payload_gup - Translates user buffer into kernel pages.

Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

9p: Add datasync to client side TFSYNC/RFSYNC for dotl

2010-10-28T14:08:49+00:00

SYNOPSIS
    size[4] Tfsync tag[2] fid[4] datasync[4]

    size[4] Rfsync tag[2]

DESCRIPTION

    The Tfsync transaction transfers ("flushes") all modified in-core data of
    file identified by fid to the disk device (or other  permanent  storage
    device)  where that  file  resides.

    If datasync flag is specified data will be fleshed but does not flush
    modified metadata unless  that  metadata  is  needed  in order to allow a
    subsequent data retrieval to be correctly handled.

Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

9p: Implement TREADLINK operation for 9p2000.L

2010-10-28T14:08:48+00:00

Synopsis

	size[4] TReadlink tag[2] fid[4]
	size[4] RReadlink tag[2] target[s]

Description
	Readlink is used to return the contents of the symoblic link
        referred by fid. Contents of symboic link is returned as a
        response.

	target[s] - Contents of the symbolic link referred by fid.

Signed-off-by: M. Mohan Kumar 
Reviewed-by: Aneesh Kumar K.V 
Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen

9p: Implement TGETLOCK

2010-10-28T14:08:47+00:00

Synopsis

    size[4] TGetlock tag[2] fid[4] getlock[n]
    size[4] RGetlock tag[2] getlock[n]

Description

TGetlock is used to test for the existence of byte range posix locks on a file
identified by given fid. The reply contains getlock structure. If the lock could
be placed it returns F_UNLCK in type field of getlock structure.  Otherwise it
returns the details of the conflicting locks in the getlock structure

    getlock structure:
      type[1] - Type of lock: F_RDLCK, F_WRLCK
      start[8] - Starting offset for lock
      length[8] - Number of bytes to check for the lock
             If length is 0, check for lock in all bytes starting at the location
            'start' through to the end of file
      pid[4] - PID of the process that wants to take lock/owns the task
               in case of reply
      client[4] - Client id of the system that owns the process which
                  has the conflicting lock

Signed-off-by: M. Mohan Kumar 
Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Venkateswararao Jujjuri 
Signed-off-by: Eric Van Hensbergen