All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: trond.myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 6/6] SUNRPC: Remove obsolete comment
Date: Mon, 09 May 2011 15:23:04 -0400	[thread overview]
Message-ID: <20110509192304.16449.52561.stgit@matisse.1015granger.net> (raw)
In-Reply-To: <20110509191859.16449.73749.stgit@matisse.1015granger.net>

Clean up.  The documenting comment at the top of net/sunrpc/clnt.c is
out of date.  We adopted BSD's RTO estimation mechanism years ago.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---

 net/sunrpc/clnt.c |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
index c0b03df..b84d739 100644
--- a/net/sunrpc/clnt.c
+++ b/net/sunrpc/clnt.c
@@ -13,10 +13,6 @@
  *	and need to be refreshed, or when a packet was damaged in transit.
  *	This may be have to be moved to the VFS layer.
  *
- *  NB: BSD uses a more intelligent approach to guessing when a request
- *  or reply has been lost by keeping the RTO estimate for each procedure.
- *  We currently make do with a constant timeout value.
- *
  *  Copyright (C) 1992,1993 Rick Sladkey <jrs@world.std.com>
  *  Copyright (C) 1995,1996 Olaf Kirch <okir@monad.swb.de>
  */


      parent reply	other threads:[~2011-05-09 19:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 19:22 [PATCH 0/6] For 2.6.40: NFSROOT fix, AF_LOCAL support Chuck Lever
2011-05-09 19:22 ` [PATCH 1/6] NFS: Revert NFSROOT default mount options Chuck Lever
2011-05-09 19:22 ` [PATCH 2/6] SUNRPC: Clean up use of curly braces in switch cases Chuck Lever
2011-05-09 19:22 ` [PATCH 3/6] SUNRPC: Rename xs_encode_tcp_fragment_header() Chuck Lever
2011-05-09 19:22 ` [PATCH 4/6] SUNRPC: Support for RPC over AF_LOCAL transports Chuck Lever
2011-05-09 19:22 ` [PATCH 5/6] SUNRPC: Use AF_LOCAL for rpcbind upcalls Chuck Lever
2011-05-09 19:23 ` Chuck Lever [this message]

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=20110509192304.16449.52561.stgit@matisse.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@netapp.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.