Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:56098 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750996AbcHCR76 (ORCPT ); Wed, 3 Aug 2016 13:59:58 -0400 Subject: Re: [PATCH 6/7] mountd: allow alternate ttl to be specified for dump_to_cache. To: NeilBrown References: <146976807524.20186.8871903418718212567.stgit@noble> <146976861681.20186.16926967483251671716.stgit@noble> Cc: "J. Bruce Fields" , Linux NFS Mailing list From: Steve Dickson Message-ID: Date: Wed, 3 Aug 2016 13:59:57 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: On 08/03/2016 01:31 PM, Steve Dickson wrote: > Hey Neil, > > This one is a bit confusing... Unless I'm missing something this > patch enables the passing of the TTL in to dump_to_cache() but > a zero is always passed in which causes the default TTL to > be used... So I guess my question is... what's the point? > Is there an upcoming patch that will actually passing a > non-default TTL Never mind... I see how its used in patch 7.. Sorry for the noise. steved.