[ewg] Re: [PATCH] mlx4_core: map sufficient ICM memory for EQs

2009-08-07 Thread Roland Dreier
Thanks, applied with a few cleanups:
  ilog2(roundup_pow_of_two())  ->  order_base_2()
  xxx * (1 << yy)  ->  xxx << yy
___
ewg mailing list
ewg@lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg


[ewg] Latest OFED 1.5 Schedule

2009-08-07 Thread Hal Rosenstock
Hi,

Is the below the latest OFED 1.5 schedule ?

http://www.openfabrics.org/txt/woody/roadmap.txt

OFED 1.5:
==
Schedule:
-
- Feature freezeJuly 15
- Alpha July 20
- Beta July 30
- RC1 Aug 12
- RC2-RCx: About every 2 weeks as needed
We usually have ~6 RCs
- GA Oct 30
Where are we in terms of these steps ? Has alpha been reached ?

-- Hal
___
ewg mailing list
ewg@lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg

Re: [ewg] Latest OFED 1.5 Schedule

2009-08-07 Thread Jon Mason
On Fri, Aug 07, 2009 at 02:51:50PM -0400, Hal Rosenstock wrote:
> Hi,
> 
> Is the below the latest OFED 1.5 schedule ?
> 
> http://www.openfabrics.org/txt/woody/roadmap.txt
> 
> OFED 1.5:
> ==
> Schedule:
> -
> - Feature freezeJuly 15
> - Alpha July 20
> - Beta July 30
> - RC1 Aug 12
> - RC2-RCx: About every 2 weeks as needed
> We usually have ~6 RCs
> - GA Oct 30
> Where are we in terms of these steps ? Has alpha been reached ?

Alpha version 4 was released on 23-Jul-2009

> 
> -- Hal

> ___
> ewg mailing list
> ewg@lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
___
ewg mailing list
ewg@lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg


Re: [ewg] [GIT PULL OFED-1.5] NFSRDMA bug fixes

2009-08-07 Thread Jon Mason
On Thu, Aug 06, 2009 at 06:38:40PM -0500, Jon Mason wrote:
> Hey Vlad,
> Please pull from
> 
> ssh://v...@sofa.openfabrics.org/home/jon/scm/ofed_kernel-1.5.git dev
> 
> It contains the following patches:

Added:

commit cc6ee58a982ca212eaf080d2a577882639210f83
Author: Jon Mason 
Date:   Fri Aug 7 15:05:50 2009 -0500

Pull in frmr iova_start truncation fix (which still does not seem to
have made it upstream).

Signed-Off-By: Jon Mason 

commit a529da97c7994fb1acbb3304376217d2e2d3189e
Author: Jon Mason 
Date:   Fri Aug 7 14:28:09 2009 -0500

JFS is being rejected as an exportable filesystem due to its lack of
get_dentry function.  In kernels older than 2.6.23, a helper function
existed for those file systems with did not have get_dentry.  This patch
re-adds that helper function to exportfs.  This enables JFS to function
as an exportable file system under NFS.

This fixes bug 1697 on SLES10sp2

Signed-Off-By: Jon Mason 

commit c5f454fce6191f8f6fdc7ec2a3cb1beb08c38444
Author: Jon Mason 
Date:   Fri Aug 7 14:24:47 2009 -0500

JFS is being rejected as an exportable filesystem due to its lack of
get_dentry function.  In kernels older than 2.6.23, a helper function
existed for those file systems with did not have get_dentry.  This patch
re-adds that helper function to exportfs.  This enables JFS to function
as an exportable file system under NFS.

This fixes bug 1697 on RHEL5.2

Signed-Off-By: Jon Mason 

commit 68afdf97804491db2891a0a30a856508617ccfc6
Author: Jon Mason 
Date:   Fri Aug 7 14:22:25 2009 -0500

JFS is being rejected as an exportable filesystem due to its lack of
get_dentry function.  In kernels older than 2.6.23, a helper function
existed for those file systems with did not have get_dentry.  This patch
re-adds that helper function to exportfs.  This enables JFS to function
as an exportable file system under NFS.

This fixes bug 1697 on RHEL5.3

Signed-Off-By: Jon Mason 

commit 6f8ab21219eb19a7194a11e4f8531a3eb15e2f5c
Author: Jon Mason 
Date:   Fri Aug 7 14:20:53 2009 -0500

JFS is being rejected as an exportable filesystem due to its lack of
get_dentry function.  In kernels older than 2.6.23, a helper function
existed for those file systems with did not have get_dentry.  This patch
re-adds that helper function to exportfs.  This enables JFS to function
as an exportable file system under NFS.

This fixes bug 1697 on RHEL5.4

Signed-Off-By: Jon Mason 

commit 11627f459cfad7083c2265964878d9fbcdc6f285
Author: Jon Mason 
Date:   Fri Aug 7 14:18:33 2009 -0500

JFS is being rejected as an exportable filesystem due to its lack of
get_dentry function.  In kernels older than 2.6.23, a helper function
existed for those file systems with did not have get_dentry.  This patch
re-adds that helper function to exportfs.  This enables JFS to function
as an exportable file system under NFS.

This fixes bug 1697 on 2.6.22

Signed-Off-By: Jon Mason 


> commit bf88ed67cb39869c1599af5be7d77425a2cbab45
> Author: Jon Mason 
> Date:   Thu Aug 6 16:50:07 2009 -0500
> 
> Getting Stale NFS file handles when running NFS tests on XFS (regardless
> of RDMA and transport).  I have determined the root of the problem to be
> the encoding/decoding of the file handle.  While other file systems have
> functions to encode the file handle, most simply copy the existing
> struct into the memory NFS provides.  When getting the dentry, they
> reference the memory in the way that the struct is.  However, XFS
> encodes by writing all of the relevant info into an array (not they way
> it is stored in the struct).  Thus, the decode function must be called
> (which was not necessary for the others based on their simplicity).  The
> decode method for xfs calls sb->s_export_op->find_exported_dentry(), so
> this must be set prior to any calls.  This was done in the original
> version of the NFS code in 2.6.22.  This issue only seems to affect
> kernels 2.6.22 and older.
> 
> This patch fixes RHEL5.2
> 
> Signed-Off-By: Jon Mason 
> 
> commit 4c3fe1ff8d9f114b98e022f86bbeaef7303314cc
> Author: Jon Mason 
> Date:   Thu Aug 6 16:48:04 2009 -0500
> 
> Getting Stale NFS file handles when running NFS tests on XFS (regardless
> of RDMA and transport).  I have determined the root of the problem to be
> the encoding/decoding of the file handle.  While other file systems have
> functions to encode the file handle, most simply copy the existing
> struct into the memory NFS provides.  When getting the dentry, they
> reference the memory in the way that the struct is.  However, XFS
> encodes by writing all of the relevant info into an array (not they way
> it is stored in the struct).  Thus, the decode function must be called
> (which was not necessary for the other