glusterfs.git/xlators/performance, branch v2.0.4

write-behind: set default window-size to 1MB.

2009-07-08T00:30:08+00:00

Signed-off-by: Anand V. Avati

performance/write-behind - bug fix in open() and create().

2009-07-02T17:14:48+00:00

open() & create() calls should reset frame->local to NULL.

bz# 104

Signed-off-by: Anand V. Avati

enhancement in write-behind

2009-06-30T23:10:34+00:00

Write calls should not be pushed to background only when the
mandatory locking is enabled, in all other cases (eg: O_SYNC,
O_DIRECT etc), we should not be 'caching' any data, but the
calls can be pushed to the background

Signed-off-by: Anand V. Avati

read-ahead: return with error code EBADF for fops on fds without file set in their context.

2009-06-11T13:29:17+00:00

- since a successful open/create will _always_ set a pointer to ra_file_t in
     context of fd, this fix makes sense.
   - an example of operations on bad fd can be afr sending read on the child
     which was down during open.

Signed-off-by: Anand V. Avati

read-ahead: unwind with a return value of -1 and error code of ENOMEM on memory allocation for ra_file in open/create

2009-06-11T13:29:17+00:00

Signed-off-by: Anand V. Avati

removed unused option 'page-size' in io-cache

2009-06-09T16:33:55+00:00

Signed-off-by: Anand V. Avati

io-cache: prevent frames from getting woken up while page is getting validated

2009-06-03T10:37:50+00:00

1. A page will be put on the inode waitq if the 'freshness' has to be verified with an fstat()

2. while the fstat is in transit, other calls (like lookup) can update ioc_inode->tv, resetting the freshness (page still on inode waitq)

3. Another read request on the same page, after the updated freshness, will wake up the page frames neglecting the fact that the page is also waiting on the inode (waiting for the fstat completion)

4. once the page's frames are woken, the page becomes elegible for purging and can get destroyed for various reasons, leaving a destroyed page pointer in the inode's waitq

5. fstat returns and hits the destroyed page pointer causing a crash

The fix is to all together disable cache hits when any page of the same inode is under validation. The otherwise cache hit will now be subjected to the ongoing validation by getting queued to the inode waitq.

Signed-off-by: Anand V. Avati

symlink-cache: fix return value of readlink

2009-05-07T07:22:45+00:00

- sc_readlink wrongly returned strlen (link) + 1 when link was present in
    cache.
  - this fixes rt #828. Since fuse_readlink_cbk does link[op_ret] = '\0', there
    was a memory corruption.

Signed-off-by: Anand V. Avati

log level fixes in read-ahead

2009-05-05T14:40:44+00:00

io-cache logging level fixes

2009-05-05T14:40:38+00:00