glusterfs.git, branch v2.0.2

Do itransform in AFR readdir.

2009-05-26T10:46:05+00:00

Signed-off-by: Anand V. Avati

Always do itransform of the inode number from the first up child.

2009-05-26T10:43:39+00:00

Signed-off-by: Anand V. Avati

add booster_fstab.h in noinst_HEADERS to fix build breakage after 'make dist'

2009-05-26T10:13:40+00:00

Signed-off-by: Anand V. Avati

ib-verbs: Set receive and send window size

2009-05-26T09:43:55+00:00

Signed-off-by: Anand V. Avati

socket: Set receive and send window size

2009-05-26T09:30:43+00:00

This is experimental. We're hoping this improve performance on
high speed links like 10GigE.

Signed-off-by: Anand V. Avati

Preserve atime/mtime during data self heal.

2009-05-26T07:11:47+00:00

Signed-off-by: Anand V. Avati

fix crash in __socket_reset. Previously iobuf_p was an allocated pointer, but since introduction of IObuf it is no more. Now iobuf has to be unref'ed instead.

2009-05-22T10:03:25+00:00

Signed-off-by: Anand V. Avati

booster: Move fstab parsing into booster from libglusterfs

2009-05-21T06:00:12+00:00

This is another attempt at fixing build problems on Solaris.
I am told that booster build is disabled on Solaris and I know
that it is disabled on Mac OS X also. Getting it to work
on both these systems is now on my TODO list, mainly
because on both these systems, we can have a glusterfs client
running without requiring FUSE.

Signed-off-by: Anand V. Avati

Change errno to EAGAIN in readv/writev

2009-05-19T15:50:31+00:00

When mandatory locks are enabled and a read/write
would block due to a lock and if the fd is opened
with O_NONBLOCK, return EAGAIN (previously EWOULDBLOCK).

Signed-off-by: Anand V. Avati

mem-pool: Restructure mem-pool behaviour

2009-05-19T15:43:22+00:00

This commit changes mem-pool behaviour to return a directly usable
address by performing the required adjustment on the address
being returned.

This is different from the previous behaviour where we're trying to fit
into the requested size, the list_head*2 also. This is not efficient
enough in terms of space but hopefully works better than not having any
mem-pool at all. Besides, I am not comfortable with mem-pool meta-data
and caller-useable memory area being the same because of the potential for
mem-pool's data structure corruption.

PS:
Please do read the comments in the code for more info during review.

Signed-off-by: Anand V. Avati