From: Jamie Lokier Subject: Re: mount options and dnotify Date: Wed, 28 Apr 2004 20:33:46 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040428193346.GB2836@mail.shareable.org> References: <1083173785.4845.29.camel@stevef95.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from mail.shareable.org ([81.29.64.88]:12416 "EHLO mail.shareable.org") by vger.kernel.org with ESMTP id S261654AbUD1Tdw (ORCPT ); Wed, 28 Apr 2004 15:33:52 -0400 To: Steve French Content-Disposition: inline In-Reply-To: <1083173785.4845.29.camel@stevef95.austin.ibm.com> List-Id: linux-fsdevel.vger.kernel.org Steve French wrote: > I was thinking of adding parsing for "notify=no" (or perhaps better to > call it dnotify=no) or "lease=no" on the cifs specific mount options to > allow control over whether these notification events only work locally > (or work for both local and remote changes) in case there are servers > out which contribute to "dnotify storms" (lots of directory change > notifications in a short period). What is the point in adding those options now? Last time I looked (kernel 2.6.5) notifications and leases only apply to local operations - there is no interaction with the server. If notifications and leases are eventually extended to communicate with the server, then you probably want an option to restrict them to local operations only, rather than disable altogether -- as your text says. In which case, "dnotify=local" and "lease=local" makes sense, no? -- Jamie