From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Layton Subject: Re: [PATCH] cifs: remove dnotify thread code Date: Fri, 9 Jan 2009 06:33:18 -0500 Message-ID: <20090109063318.04f260d1@tleilax.poochiereds.net> References: <1231424128-5598-1-git-send-email-jlayton@redhat.com> <524f69650901080623s228c343eka791c089c878167@mail.gmail.com> <20090109000708.GC12848@shareable.org> <524f69650901081932m2912ab73x147221f721194f8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "Jamie Lokier" , linux-cifs-client@lists.samba.org, linux-fsdevel@vger.kernel.org To: "Steve French" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:49733 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751770AbZAILdb (ORCPT ); Fri, 9 Jan 2009 06:33:31 -0500 In-Reply-To: <524f69650901081932m2912ab73x147221f721194f8@mail.gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, 8 Jan 2009 21:32:09 -0600 "Steve French" wrote: > What worries me most about losing the ability to add directory change > notification in the future (without putting the entry point back) the > lack of directory change notification is quite visible to the user > when an open directory object on the desktop (gnome or kde) does not > automatically refresh within a few seconds as files are added on the > remote system (or on another client). > > The old cifs implementation was broken (partially implemented) but it > was "dead code" so was harmless (it required configuring with > CONFIG_CIFS_EXPERIMENTAL and turning on a run time flag in > /proc/fs/cifs to enable it) but it might not have been too bad to > finish the implementation. > This patch doesn't remove any capability of the current code. It just gets rid of this kthread that doesn't do anything useful. There's nothing stopping us from putting it back later once we have working dir notification, but until then it's just doing unnecessary wakeups. -- Jeff Layton