linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: "Steve French" <smfrench@gmail.com>
Cc: "Jamie Lokier" <jamie@shareable.org>,
	linux-cifs-client@lists.samba.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] cifs: remove dnotify thread code
Date: Fri, 9 Jan 2009 13:07:57 -0500	[thread overview]
Message-ID: <20090109130757.11ec9d81@tleilax.poochiereds.net> (raw)
In-Reply-To: <524f69650901090818w7f367832vb9d0979714c3c609@mail.gmail.com>

On Fri, 9 Jan 2009 10:18:28 -0600
"Steve French" <smfrench@gmail.com> wrote:

> On Fri, Jan 9, 2009 at 5:33 AM, Jeff Layton <jlayton@redhat.com> wrote:
> > On Thu, 8 Jan 2009 21:32:09 -0600
> > "Steve French" <smfrench@gmail.com> wrote:
> > 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.
> Al's patch removes the ability for a network or cluster file system to
> handle directory change notification in the future ... (AFAIK KDE,
> GNOME still use this fcntl) so we won't be able to fix the fcntl to
> work where it matters most (network or cluster environments) in the
> future without reverting the patch.
> 

Right. By "this patch", I meant the one that I sent.

Al's concerns seem valid though. You may be able to convince him to
add back in a dir_notify type interface to the VFS later but I imagine
it will need some redesign to address the problems he noted.

-- 
Jeff Layton <jlayton@redhat.com>

  reply	other threads:[~2009-01-09 18:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 14:15 [PATCH] cifs: remove dnotify thread code Jeff Layton
2009-01-08 14:23 ` Steve French
2009-01-08 14:51   ` Jeff Layton
2009-01-09  0:07   ` Jamie Lokier
2009-01-09  1:28     ` Jeff Layton
2009-01-10  1:35       ` Jamie Lokier
2009-01-10  1:41       ` Jamie Lokier
2009-01-10 18:19         ` Steve French
2009-01-09  3:32     ` Steve French
2009-01-09 11:33       ` Jeff Layton
2009-01-09 16:18         ` Steve French
2009-01-09 18:07           ` Jeff Layton [this message]
2009-01-09 18:18       ` Al Viro

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=20090109130757.11ec9d81@tleilax.poochiereds.net \
    --to=jlayton@redhat.com \
    --cc=jamie@shareable.org \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=smfrench@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).