On Thu, Nov 06, 2014 at 04:58:34PM -0500, Jeff Layton wrote: > On Thu, 6 Nov 2014 15:20:09 -0500 > "J. Bruce Fields" <bfields@xxxxxxxxxxxx> wrote: > > > On Tue, Oct 28, 2014 at 02:24:11PM -0400, Jeff Layton wrote: > > > These patches add some tracepoints that I recently used when tracking > > > down the hang that Christoph reported recently. At this point, I still > > > haven't followed the trail to completion, but I think the problem is > > > not likely to be in the RPC code. > > > > > > Please consider these for v3.19? Some of these are for client RPC and > > > some for server-side. I'll assume that Trond will merge these, but > > > review by others would be appreciated as well. > > > > Looks fine to me, thanks, I'll assume Trond's applying all three unless > > I hear otherwise. > > > > (Separate issue: the server-side rpc dprintk's need review: they're much > > too frequent to be useful, I think.) > > > > Thanks. > > Yeah. Probably best to just slowly phase those out in favor of > tracepoints. Is there any way to do that that's less labor intensive? No idea. I'm hoping we can just get of some of them entirely, but I don't know, I really haven't tried to look through them. (I've just noticed that there's usually a ton of output, and recall it interfering with testing in some cases--admittedly I might just be remembering cases where someone was trying to use a slow serial interface for logging.) --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
