glusterfs.git/xlators/performance/write-behind, branch v3.4.5

performance/write-behind: invoke request queue processing if

2013-09-10T08:22:49+00:00

we find fd marked bad while trying to fulfill lies.

* flush was queued behind some unfulfilled write.
* A previously wound write returned an error and hence fd was marked
  bad with corresponding error.
* wb_fulfill_head (invocation probably rooted in wb_flush), before
  winding checks for failures of previous writes and since there was a
  failure, calls wb_head_done without even winding one request in head.
* wb_head_done unrefs all the requests in list "head".
* since flush was last operation on fd (and most likely last operation
  on inode itself), no one invokes wb_process_queue and flush is stuck
  in request queue for eternity.

Change-Id: I3b5b114a1c401d477dd7ff64fb6119b43fda2d18
BUG: 988642
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.org/5883
Tested-by: Gluster Build System

call-stub: internal refactor

2013-09-05T13:27:05+00:00

- re-structure members of call_stub_t with new simpler layout
- easier to inspect call_stub_t contents in gdb now
- fix a bunch of double unrefs and double frees in cbk stub
- change all STACK_UNWIND to STACK_UNWIND_STRICT and thereby fixed
  a lot of bad params
- implement new API call_unwind_error() which can even be called on
  fop_XXX_stub(), and not necessarily fop_XXX_cbk_stub()

Change-Id: Idf979f14d46256af0afb9658915cc79de157b2d7
BUG: 846240
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/4520
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/5820
Reviewed-by: Raghavendra Bhat

performance/write-behind: Enable write-behind when strict_O_DIRECT is not set.

2013-05-30T00:04:11+00:00

When open() with O_DIRECT happens, write-behind was being disabled for the
fd irrespective of strict_O_DIRECT option. This commit disables write-behind
only when strict_O_DIRECT is enabled.

Change-Id: Ieef180e52910c3bf64d46b26b0e5dc3b8542f6d2
BUG: 923556
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/4697
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/5108
Reviewed-by: Anand Avati

performance/write-behind: guarantee non-overlapping concurrent writes

2013-03-07T07:30:14+00:00

Maintain a list of writes (either written behind or SYNC) which are
currently "in progress" (i.e, STACK_WIND'ed towards server) and hold
off any new STACK_WIND of write (either written behind or SYNC) which
overlaps with any of the "in progress" writes.

This is a guarantee which AFR's eager-lock depends upon (though not
strictly a write-behind requirement)

Change-Id: Icedd0b51b440366a906dc9223d62b7fd6ef2ca03
BUG: 857673
Original-author: Anand Avati 
Signed-off-by: Anand Avati 
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/4642
Tested-by: Gluster Build System

performance/write-behind: mark fd bad if any written behind writes fail

2013-03-07T05:18:00+00:00

BUG: 765473
Change-Id: I1ddd6ef9f5361aed96f97aa1344823836c6ddecb
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.org/4630
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy

Use proper libtool option -avoid-version instead of bogus -avoidversion

2013-02-07T23:12:56+00:00

Change-Id: I1c9541058c7d07786539a3266ca125a6a15287d8
BUG: 859835
Signed-off-by: Anand Avati 
Original-author: Kacper Kowalik (Xarthisius) 
Signed-off-by: Kacper Kowalik (Xarthisius) 
Reviewed-on: http://review.gluster.org/3967
Tested-by: Gluster Build System

performance/write-behind: do not try to take LOCK in forget

2013-02-03T22:09:49+00:00

LOCK attempt in wb_forget is unnecessary

Change-Id: Ibdedc23d0c829c34aedd6fc5bc0e0a584b832514
BUG: 903566
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/4423
Reviewed-by: Anand Avati 
Tested-by: Gluster Build System

glusterd/cli: Updated the options descriptions for "volume set help"

2013-01-22T07:03:57+00:00

Change-Id: I0db00b7334bb9707ab48bd661ac03a3ad818d6e4
BUG: 893458
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/4393
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

write-behind: fixes issues with iobuf length for large writes

2012-12-13T22:46:42+00:00

Use of an unsigned type in some calculations of size would lead to segmentation
faults, if several large adjacent writes came in concurrently.

Also, improves buffer allocation code to take the size required into account.

Credits for the patch go to Amar.

Change-Id: I8a09c52d49909e4ee8e7d4dcfa02ec33ea36a551
BUG: 880948
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/4307
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

fix memory leaks

2012-12-04T20:14:28+00:00

* write-behind: free the inode context in wb_forget
* distribute: in readdirp callback put the allocated context to the inode
* distribute: check if the layout is NULL before accessing it in layout_unref

Change-Id: I7698f81b85b99d06bf6b01fc1a6e51e1593b5e27
BUG: 790709
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/4250
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati