glusterfs.git/xlators, branch v2.0.7

cluster/afr: dir-write: Fix inode number handling.

2009-09-29T02:36:12+00:00

create, mkdir, symlink, mknod: Prefer to return itransform'd inode number
from the first_up_child. If not, fall back on any other child that returned
succcess.

link, rename: Return the same inode number that
was passed as part of loc_t.

Also adds a new member to afr_local_t, local->first_up_child
which is initialized at the start of the transaction. This
fixes the race where a subvolume might go down during the transaction
and thus have the first_up_child change.

Signed-off-by: Anand V. Avati 

BUG: 285 ("first up child" can change during a transaction)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=285

write-behind: check for NULL file pointer in flush callback

2009-09-24T14:13:41+00:00

Signed-off-by: Anand V. Avati 

BUG: 260 (ls on booster VMP results in error: "File descriptor in bad state")
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=260

performance/write-behind: Add NULL checks for file pointer.

2009-09-24T12:19:37+00:00

Signed-off-by: Anand V. Avati 

BUG: 260 (ls on booster VMP results in error: "File descriptor in bad state")
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=260

performance/write-behind: Add a NULL check for request->stub before checking request->stub->fop.

2009-09-24T08:19:16+00:00

- for non-write wind requests, the request structure outlives the stub.
    The call stub is destroyed when stack is wound but request is destroyed
    only when the reply has come.
    (for writes, both stub and request are destroyed when refcount becomes 0,
     which happens only when the write operation is stack unwound and a reply
     for the write operation has come from underlying translators, for non-write
     unwind requests the request is first destroyed before resuming the stub).

Signed-off-by: Anand V. Avati 

BUG: 280 (simple stripe, with write-behind set up, when dbench is run client crashes.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=280

fuse: emit a flush from release if we didn't get an adjacent FLUSH message from the kernel

2009-09-23T16:19:29+00:00

Signed-off-by: Anand V. Avati 

BUG: 223 (flush not sent)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=223

performance/write-behind: store currently aggregated data size in wb_file

2009-09-23T08:47:27+00:00

- this helps us to not traverse the request list whenever we need currently
    aggregated data in the queue

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

performance/write-behind: store the current window size in wb_file.

2009-09-23T08:47:23+00:00

- this would increase the performance since we don't have to traverse the
    request list every time we need the current window size.

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

performance/write-behind: reduce usage of iov_length.

2009-09-23T08:47:20+00:00

- request structure now holds a member write_size which is initialised at the
    time of request creation and used later.

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

performance/write-behind: add option "enable-trickling-writes".

2009-09-22T13:14:30+00:00

- With this option enabled, writes are stack-wound even though not enough
    data is aggregated, provided there are no write-requests which are
    stack-wound but reply is yet to come. The reason behind this option
    is to make use of the network, which is relatively free (with no writes
    or replies in transit). However, with non-standard block-sizes of writes
    the performance can actually degrade. Hence making this configurable.

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

performance/write-behind: reduce traversal of request list during wb_mark_winds.

2009-09-22T13:14:26+00:00

- move all the decision making code to __wb_can_wind.
  - don't continue traversing the request list, once we know any of the
    following conditions are true:
    * requests other than write are present in queue.
    * writes are happening at non-contiguous offsets.
    * there are no write requests, which are wound to server but not yet
      received the reply.
    * enough data is aggregated for writing.

Signed-off-by: Anand V. Avati 

BUG: 276 (write behind needs to be optimized.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276