glusterfs.git/xlators/performance, branch v3.0.3

performance/io-threads: Support for Solaris.

2010-03-03T14:40:01+00:00

Signed-off-by: Vijay Bellur 
Signed-off-by: Anand V. Avati 

BUG: 621 (3.0.2 GlusterFS fails on Solaris 10)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=621

performance/write-behind: fix data corruption while aggregating the adjacent contiguous iobufs into a single iobuf

2010-02-23T07:39:47+00:00

- while aggregating, we should make sure that the destination has enough
   memory. __wb_collapse_write_bufs assumed that destination vector's iov_base
   was aligned to the start of an iobuf and hence memory of page_size is
   available for aggregation. This assumption is not always true, like in the
   configuration consisting afr->write->io-cache (afr is on top). Refer to the
   bug url for more details.

Signed-off-by: Raghavendra G 
Signed-off-by: Anand V. Avati 

BUG: 542 (write-behind crashes)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=542

performance/write-behind: refactor __wb_collapse_write_bufs

2010-02-23T07:39:40+00:00

- refactor done to remove duplicated code.

Signed-off-by: Raghavendra G 
Signed-off-by: Anand V. Avati 

BUG: 542 (write-behind crashes)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=542

common-utils: gf_log2 handles 0 input

2010-02-22T16:51:44+00:00

Signed-off-by: Anand V. Avati 
Signed-off-by: Anand V. Avati 
Signed-off-by: Anand V. Avati 

BUG: 583 (filesystem access hangs while deleting large files)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=583

write-behind: fix 'option enable-trickling-writes'

2010-01-26T11:47:32+00:00

fix logic in __wb_mark_winds to properly initialize incomplete_writes
and conditionally check based on enable_trickling_writes flag

Signed-off-by: Anand V. Avati 
Signed-off-by: Anand V. Avati 

BUG: 547 (write-behind enable-trickling-writes working?)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=547

Added null checks in "fini"

2009-12-18T16:41:29+00:00

Signed-off-by: Harshavardhana 
Signed-off-by: Vijay Bellur 

BUG: 364 (Segfault in io-cache)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=364

Revert "performance/write-behind: Changed default value of option disable-till to 0"

2009-12-06T21:51:03+00:00

This reverts commit e6c35f74ff4a204cf016ebf201a2630b331f9434.

This commit is found to trigger spurious self heal by causing flush and writev to get
reordered. Reverting as a workaround.

performance/stat-prefetch: remove the usage of THIS.

2009-12-06T10:30:24+00:00

Signed-off-by: Raghavendra G 
Signed-off-by: Anand V. Avati 

BUG: 221 (stat prefetch implementation)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

performance/stat-prefetch: fix memory leak.

2009-12-06T10:30:21+00:00

- rbt_hash_remove only removes entry from the hash table. It does not free
    the data.

Signed-off-by: Raghavendra G 
Signed-off-by: Anand V. Avati 

BUG: 438 (Memory leak)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=438

performance/stat-prefetch: don't check whether previous lookups have been failed in sp_process_inode_ctx.

2009-12-05T12:21:29+00:00

We need this patch for following reasons:
   1. The inode used in the successful lookup call may not be the one passed to
      fops operating on path. This may happen, if revalidate of inode is failed,
      but the lookup itself succeeds (in case of reavalidate failures, fuse
      sends a fresh lookup using new inode) and since inode_link, if there is an
      inode already associated with a path retains it.
   2. Only fops that "wait" in stat-prefetch for a lookup which is already in
      progress, need to check for the result of the lookup they are waiting on,
      before resuming and sp_process_inode_ctx is _not_ used in such contexts.

Signed-off-by: Raghavendra G 
Signed-off-by: Anand V. Avati 

BUG: 428 (looks like stat cache not upto date..)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=428