- 15 Mar, 2011 40 commits
-
-
Aneesh Kumar K.V authored
Changes to make sure writeback fid is owned by root Signed-off-by:
Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> Signed-off-by:
Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com> Signed-off-by:
Eric Van Hensbergen <ericvh@gmail.com>
-
Aneesh Kumar K.V authored
change file attribute can result in making the file readonly. So flush the dirty pages before that. Signed-off-by:
-
Aneesh Kumar K.V authored
We need to call vmtruncate before 9p setattr operation, otherwise we could write back some dirty pages between setattr with ATTR_SIZE and vmtruncate causing some truncated pages to be written back to server Signed-off-by:
-
Aneesh Kumar K.V authored
With caching enabled, we need to make sure we don't update inode->i_size via stat2inode because we could have dirty data which is not yet written to the server Signed-off-by:
-
Aneesh Kumar K.V authored
Add necessary #ifndef #endif blocks to avoid mulitple inclusion of same headers Signed-off-by:
-
Aneesh Kumar K.V authored
This is similar to what ceph, ocfs2 and nfs does http://kerneltrap.org/mailarchive/linux-fsdevel/2008/4/18/1498534 May be we should get vfs fixed Signed-off-by:
-
Aneesh Kumar K.V authored
One successfull directory operation we would have changed directory inode attribute. So mark them invalid Signed-off-by:
-
Aneesh Kumar K.V authored
We need to revalidate . and .. entries also Signed-off-by:
-
Aneesh Kumar K.V authored
rename, unlink and setattr can result in update of inode attribute. So mark the cached copy invalid Signed-off-by:
-
Aneesh Kumar K.V authored
With cached mode some of the file system operation result in updating inode attributes (ctime). Add support for marking inode attribute invalid in such cases so that we fetch the updated inode attribute on dentry revalidation. Signed-off-by:
-
Aneesh Kumar K.V authored
Signed-off-by:
-
Aneesh Kumar K.V authored
Signed-off-by:
-
Aneesh Kumar K.V authored
We want to immediately drop the inode in non cached mode Signed-off-by:
-
Aneesh Kumar K.V authored
Signed-off-by:
-
Aneesh Kumar K.V authored
Only update inode i_size when we write towards end of file. Signed-off-by:
-
Aneesh Kumar K.V authored
We want to enable readahead in cached mode Signed-off-by:
-
Aneesh Kumar K.V authored
Signed-off-by:
-
Aneesh Kumar K.V authored
Switch to the fscache code to v9fs_inode. We will later use v9fs_inode in cache=loose mode to track the inode cache validity timeout. Ie if we find an inode in cache older that a specific jiffie range we will consider it stale Signed-off-by:
-
Aneesh Kumar K.V authored
simple_getattr does set stat.st_blocks to a value derived from nrpages. That is not correct with 9p Signed-off-by:
-
Aneesh Kumar K.V authored
We didn't add the inode to inode hash in 9p. We need to do that to get sync to work, otherwise __mark_inode_dirty will not add the inode to super block's dirty list. Signed-off-by:
-
Aneesh Kumar K.V authored
Signed-off-by:
-
Aneesh Kumar K.V authored
FIXME!! what about dotu ? Signed-off-by:
-
Aneesh Kumar K.V authored
Signed-off-by:
-
Aneesh Kumar K.V authored
We should not mark file system synchronous if mounted cache=* option Signed-off-by:
-
Aneesh Kumar K.V authored
Update the comment to indicate that we don't want to cache negative dentries. Signed-off-by:
-
Aneesh Kumar K.V authored
We can now support writeable mmaps. Based on the original patch from Badari Pulavarty <pbadari@us.ibm.com> Signed-off-by:
-
Aneesh Kumar K.V authored
The fid attached to inode will be opened O_RDWR mode and is used for dirty page writeback only. Signed-off-by:
-
Aneesh Kumar K.V authored
We add read write helper function here which will be used later by the mmap patch Signed-off-by:
-
Aneesh Kumar K.V authored
We need to call fscache_wait_on_page_write in launder_page for fscache Signed-off-by:
-
Aneesh Kumar K.V authored
We need to ihold even in cached mode Signed-off-by:
-
Aneesh Kumar K.V authored
We need to call v9fs_cache_inode_set_cookie in create path also Signed-off-by:
-
Aneesh Kumar K.V authored
With the old code we were not setting the file->f_op with cached file operations during creat. (format correction by jvrao@linux.vnet.ibm.com) Signed-off-by:
-
Venkateswararao Jujjuri (JV) authored
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 (JV) authored
This takes care of copying out error buffers from user buffer payloads when we are using zero copy. This happens because the only payload buffer the server has to respond to the request is the user buffer given for the zero copy read. Because we only use zerocopy when the amount of data to transfer is greater than a certain size (currently 4K) and error strings are limited to ERRMAX (currently 128) we don't need to worry about there being sufficient space for the error to fit in the payload. Signed-off-by:
-
Venkateswararao Jujjuri (JV) authored
Modify p9_client_readdir() to check the transport preference and act according If the preference is P9_TRANS_PREF_PAYLOAD_SEP, send the payload separately instead of putting it directly on PDU. Signed-off-by:
-
Venkateswararao Jujjuri (JV) authored
Modify p9_client_write() to check the transport preference and act accordingly. If the preference is P9_TRANS_PREF_PAYLOAD_SEP, send the payload separately instead of putting it directly on PDU. Signed-off-by:
-
Venkateswararao Jujjuri (JV) authored
Modify p9_client_read() to check the transport preference and act accordingly. If the preference is P9_TRANS_PREF_PAYLOAD_SEP, send the payload separately instead of putting it directly on PDU. Signed-off-by:
-
Venkateswararao Jujjuri (JV) authored
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 (JV) authored
Modify p9_virtio_request() and req_done() functions to support additional payload sent down to the transport layer through tc->pubuf and tc->pkbuf. Signed-off-by:
-
Venkateswararao Jujjuri (JV) authored
This will be used by the transport layer to determine the out going request type. Transport layer uses this information to correctly place the mapped pages in the PDU. Patches following this will make use of this to achieve zero copy. Signed-off-by:
-
