From mboxrd@z Thu Jan 1 00:00:00 1970 From: Goldwyn Rodrigues Subject: [PATCH] [TRIVIAL] Code comments update in NFS Date: Fri, 17 Feb 2006 15:57:50 +0000 Message-ID: <241c7a2b0602170757x3e5259abyea60fb9f479dd53d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from zproxy.gmail.com ([64.233.162.198]:3411 "EHLO zproxy.gmail.com") by vger.kernel.org with ESMTP id S932380AbWBQP5v convert rfc822-to-8bit (ORCPT ); Fri, 17 Feb 2006 10:57:51 -0500 Received: by zproxy.gmail.com with SMTP id o37so428093nzf for ; Fri, 17 Feb 2006 07:57:51 -0800 (PST) To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, okir@monad.swb.de, trivial@kernel.org Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, read_cache_mtime is no longer used in nfs_inode. This patch removes references of read_cache_mtime in the code comments. Signed-off-by: Goldwyn Rodrigues --- a/include/linux/nfs_fs.h +++ b/include/linux/nfs_fs.h @@ -118,8 +118,7 @@ struct nfs_inode { unsigned long cache_validity; /* bit mask */ /* - * read_cache_jiffies is when we started read-caching this inode, - * and read_cache_mtime is the mtime of the inode at that time. + * read_cache_jiffies is when we started read-caching this inode. * attrtimeo is for how long the cached information is assumed * to be valid. A successful attribute revalidation doubles * attrtimeo (up to acregmax/acdirmax), a failure resets it to @@ -128,11 +127,6 @@ struct nfs_inode { * We need to revalidate the cached attrs for this inode if * * jiffies - read_cache_jiffies > attrtimeo - * - * and invalidate any cached data/flush out any dirty pages if - * we find that - * - * mtime != read_cache_mtime */ unsigned long read_cache_jiffies; unsigned long attrtimeo;