Linux NFS development
 help / color / mirror / Atom feed
From: Greg Banks <gnb@sgi.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Neil Brown <neilb@suse.de>,
	"Talpey, Thomas" <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: Thu, 24 May 2007 01:14:13 +1000	[thread overview]
Message-ID: <20070523151412.GO14076@sgi.com> (raw)
In-Reply-To: <4651ACDA.7050207@oracle.com>

On Mon, May 21, 2007 at 10:29:46AM -0400, Chuck Lever wrote:
> Neil Brown wrote:
> >On Monday May 21, gnb@sgi.com wrote:
> >>In any case I'm happy to do whatever is necessary in the transport
> >>patchset,  but I'd appreciate Neil's guidance on which approach he'd
> >>prefer before I go in with the scalpel.  Neil?
> >
> >I cannot immediately see the value in having different debug bits for
> >the socket transport code and the RDMA transport code.  The key
> >question is "When would you want to see the debugging from one, but
> >not from the other", and I cannot see when that would be.  Almost
> >certainly if you are testing one transport, you will not be using the
> >other, so it will not contribute any noise.
> 
> That's how I did it in the client transport switch.  One bit enables 
> debug messages for all transports.
> 
> >So I suspect we should simply
> >#define RPCDBG_FACILITY	RPCDBG_SVCSOCK
> 
> That's expedient, but I suggest you rename the flag to something less 
> specific to sockets.

Aah, I see now.  That's very easy.  How's this?



Rename RPCDBG_SVCSOCK to RPCDBG_SVCXPRT to reflect its
new more generic nature.

Signed-off-by: Greg Banks <gnb@melbourne.sgi.com>
---

 include/linux/sunrpc/debug.h |    2 +-
 net/sunrpc/svcsock.c         |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Index: linux/include/linux/sunrpc/debug.h
===================================================================
--- linux.orig/include/linux/sunrpc/debug.h	2007-04-26 13:08:32.000000000 +1000
+++ linux/include/linux/sunrpc/debug.h	2007-05-24 01:09:11.427405573 +1000
@@ -20,7 +20,7 @@
 #define RPCDBG_PMAP		0x0020
 #define RPCDBG_SCHED		0x0040
 #define RPCDBG_TRANS		0x0080
-#define RPCDBG_SVCSOCK		0x0100
+#define RPCDBG_SVCXPRT		0x0100
 #define RPCDBG_SVCDSP		0x0200
 #define RPCDBG_MISC		0x0400
 #define RPCDBG_CACHE		0x0800
Index: linux/net/sunrpc/svcsock.c
===================================================================
--- linux.orig/net/sunrpc/svcsock.c	2007-05-23 22:39:53.000000000 +1000
+++ linux/net/sunrpc/svcsock.c	2007-05-24 01:09:15.574878967 +1000
@@ -73,7 +73,7 @@
  *
  */
 
-#define RPCDBG_FACILITY	RPCDBG_SVCSOCK
+#define RPCDBG_FACILITY	RPCDBG_SVCXPRT
 
 
 static struct svc_sock *svc_setup_socket(struct svc_serv *, struct socket *,

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

  reply	other threads:[~2007-05-23 15:14 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
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 [this message]
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=20070523151412.GO14076@sgi.com \
    --to=gnb@sgi.com \
    --cc=Thomas.Talpey@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=pleckie@melbourne.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox