All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gnb@sgi.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: Neil Brown <neilb@suse.de>, Tom Talpey <Thomas.Talpey@netapp.com>,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>,
	Peter Leckie <pleckie@melbourne.sgi.com>
Subject: Re: [RFC, PATCH 9/15] knfsd: add RDMA debug class to rpc_debug bitfield
Date: Mon, 21 May 2007 13:19:40 +1000	[thread overview]
Message-ID: <20070521031940.GF7482@sgi.com> (raw)
In-Reply-To: <1179510345.23385.122.camel@trinity.ogc.int>

On Fri, May 18, 2007 at 12:45:45PM -0500, Tom Tucker wrote:
> 
> Add a bit to the rpc_debug bit field for RDMA transport
> debug messages and sysctl definitions for configuration
> and statistics files in /proc/sys/sunrpc/svc_rdma.
> 
> Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
> ---
> 
>  include/linux/sunrpc/debug.h |   15 +++++++++++++++
>  1 files changed, 15 insertions(+), 0 deletions(-)
> 
> diff --git a/include/linux/sunrpc/debug.h b/include/linux/sunrpc/debug.h
> index fc3a5dd..9bf7381 100644
> --- a/include/linux/sunrpc/debug.h
> +++ b/include/linux/sunrpc/debug.h
> @@ -24,6 +24,7 @@ #define RPCDBG_SVCSOCK		0x0100
>  #define RPCDBG_SVCDSP		0x0200
>  #define RPCDBG_MISC		0x0400
>  #define RPCDBG_CACHE		0x0800
> +#define RPCDBG_RDMA		0x1000
>  #define RPCDBG_ALL		0x7fff

Fine.  Did you update the rpc_debug program in nfs-utils, which also
knows about these debug bits?

>  #ifdef __KERNEL__
> @@ -93,6 +94,20 @@ enum {
>  	CTL_RDMA_MAXINLINEWRITE,
>  	CTL_RDMA_WRITEPADDING,
>  	CTL_RDMA_MEMREG,
> +	CTL_SVCRDMA,
> +	CTL_RDMA_MAX_REQUESTS,
> +	CTL_RDMA_MAX_REQ_SIZE,
> +	CTL_RDMA_ORD,
> +	CTL_RDMA_READ_THROTTLE,
> +	CTL_RDMA_STAT_RECV,
> +	CTL_RDMA_STAT_READ,
> +	CTL_RDMA_STAT_WRITE,
> +	CTL_RDMA_STAT_SQ_STARVE,
> +	CTL_RDMA_STAT_RQ_STARVE,
> +	CTL_RDMA_STAT_RQ_POLL,
> +	CTL_RDMA_STAT_RQ_PROD,
> +	CTL_RDMA_STAT_SQ_POLL,
> +	CTL_RDMA_STAT_SQ_PROD
>  };
>  
>  #endif /* _LINUX_SUNRPC_DEBUG_H_ */

This is fine, but one tiny nit: you have the makings of two patches
here.  This hunk belongs with the patch that uses the new defines
and registers the sysctls.

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
Apparently, I'm Bedevere.  Which MPHG character are you?
I don't speak for SGI.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2007-05-21  3:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 17:45 [RFC, PATCH 9/15] knfsd: add RDMA debug class to rpc_debug bitfield Tom Tucker
2007-05-18 18:52 ` Chuck Lever
2007-05-18 18:57   ` Tom Tucker
2007-05-21  3:19 ` Greg Banks [this message]
2007-05-21  3:31   ` Tom Tucker
2007-05-21  4:16     ` Greg Banks
2007-05-21  4:39       ` Neil Brown
2007-05-21 14:29         ` Chuck Lever
2007-05-23 15:14           ` Greg Banks
2007-05-23 20:27             ` Chuck Lever

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070521031940.GF7482@sgi.com \
    --to=gnb@sgi.com \
    --cc=Thomas.Talpey@netapp.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=pleckie@melbourne.sgi.com \
    --cc=tom@opengridcomputing.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.