From: Greg Banks <gnb@sgi.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: NeilBrown <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: Mon, 21 May 2007 14:16:18 +1000 [thread overview]
Message-ID: <20070521041617.GG7482@sgi.com> (raw)
In-Reply-To: <C2767CB3.30B42%tom@opengridcomputing.com>
On Sun, May 20, 2007 at 10:31:15PM -0500, Tom Tucker wrote:
>
> BTW, Chuck Lever also pointed out that we should probably have a generic
> RPCDBG_XPRT debug flag instead of RPCDBG_RDMA.
So he did. Serves me right for not reading all my email before
replying.
> I think he's right. I think
> this should be part of the transport patchset that you're working on. Do you
> agree?
I'm a little confused as to precisely what is suggested.
Currently we have an existing RPCDBG_SVCSOCK which enables dprintks
in both the generic transport code and in the sockets-specific code
too; this is hard to separate because all the code is intermingled in
the one file svcsock.c.
If the suggestion is to have separate bits for the sockets-specific
and the generic code, then the two painful alternatives seem to be
a) splitting the sockets and generic code into separate .c files, or
b) changing half the dprintk()s in svcsock.c to dfprintks().
I wasn't planning to do either of those anytime soon; either would
be a significant change.
I think the ideal case would be a total of 3 debug bits: one for the
generic transport code, one for the sockets transport-specific code and
one for the RDMA transport-specific code. Getting there isn't easy.
However given that the new svc_rdma* code is large and in separate
files, giving it it's own RPCDBG_RDMA bit, as you've already done,
is easy and useful and a step in the right direction.
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?
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
next prev parent reply other threads:[~2007-05-21 4:16 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 [this message]
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=20070521041617.GG7482@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.