Date: Wed, 11 Nov 2020 11:45:10 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: stable@freebsd.org Subject: Re: kqueue and NFS Message-ID: <634878874.26.1605091510541@localhost> In-Reply-To: <C3ED9425-1FFA-48F3-A60D-3A09411AC50D@cs.huji.ac.il>
index | next in thread | previous in thread | raw e-mail
Hi, I don't think NFS has the possibility to push notifications about changes in the filesystem to the clients. NFSv3 is stateless so the server does not even know about the clients. NFSv4 I don't know much about, but I have never heard of notifications. So for NFS kqueue would only trigger if the change is on the same client as where the kqueue is lurking. Otherwise you could run some daemon on the server which pushes the notifications out of band of the NFS protocol to the clients. Which probably gives interesting results together with the caching of the NFS client. But that is another story we see at work. (postfix -> you have mail! -> NFS -> imap -> no you don't -> O yes, you have. :-) ) Regards, Ronald. Van: Daniel Braniss <danny@cs.huji.ac.il> Datum: woensdag, 11 november 2020 09:40 Aan: stable@freebsd.org Onderwerp: kqueue and NFS > > Hi, > I have a vague recollection that kqueue does not work for NFS files, > any chance that this will be made possible? > > cheers, > danny > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > From owner-freebsd-stable@freebsd.org Wed Nov 11 13:37:06 2020 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5E6F32EA065 for <freebsd-stable@mailman.nyi.freebsd.org>; Wed, 11 Nov 2020 13:37:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4CWQkn6nCVz4n2P for <freebsd-stable@freebsd.org>; Wed, 11 Nov 2020 13:37:05 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.nyi.freebsd.org (Postfix) id E88F12EA2F3; Wed, 11 Nov 2020 13:37:05 +0000 (UTC) Delivered-To: stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E855F2EA064 for <stable@mailman.nyi.freebsd.org>; Wed, 11 Nov 2020 13:37:05 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CWQkn595Vz4myt for <stable@freebsd.org>; Wed, 11 Nov 2020 13:37:05 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=5lWyamj2zAhN/3mT1/h3IHuPoPyIhIss75rCkhnZaY4=; b=J5s6HqyVxDG8MVcTmAU2nfUerIgVEpAM7L/sWj1XtDMURRsL2rkrV0JbyxNx2cADHJ/CC9Y4P2RvUQel6GaXK5rgTVzSvFB8k0hJ+EGivIeaDS8BAuf2DnflXjKyXIKcyQr7fFleX/L6l+5bYbX0veNeDngN1Rg3c2MGa0g55CGKBonhmswR4pH0zyWcpeE/CNocgznQuzCKuAIxDWLVbZReC6d8JGDPgIcIJ6wC11lgkA7r5006LSh8uLEMTRMSWkDf1FBCuKKBQMEdVjtp0EvM/y/Ol/bI1TJL4Dawp8vt/eiHI1VuYNwly5JSVMSnIMWTgXhoKeCYtI9BjXJicw==; Received: from mbpro2.bk.cs.huji.ac.il ([132.65.179.20]) by kabab.cs.huji.ac.il with esmtp id 1kcqJ2-000Kep-J6; Wed, 11 Nov 2020 15:37:00 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.0.3.2.82\)) Subject: Re: kqueue and NFS From: Daniel Braniss <danny@cs.huji.ac.il> X-Priority: 3 (Normal) In-Reply-To: <634878874.26.1605091510541@localhost> Date: Wed, 11 Nov 2020 15:37:00 +0200 Cc: stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6262B2F9-39CF-4326-B391-1A23AE65DEF2@cs.huji.ac.il> References: <C3ED9425-1FFA-48F3-A60D-3A09411AC50D@cs.huji.ac.il> <634878874.26.1605091510541@localhost> To: Ronald Klop <ronald-lists@klop.ws> X-Mailer: Apple Mail (2.3654.0.3.2.82) X-Rspamd-Queue-Id: 4CWQkn595Vz4myt X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 11 Nov 2020 13:37:06 -0000 hi, > On 11 Nov 2020, at 12:45, Ronald Klop <ronald-lists@klop.ws> wrote: >=20 > Hi, >=20 > I don't think NFS has the possibility to push notifications about = changes in the filesystem to the clients. NFSv3 is stateless so the = server does not even know about the clients. NFSv4 I don't know much = about, but I have never heard of notifications. >=20 I now remember having a similar chat with Rick some years ago. > So for NFS kqueue would only trigger if the change is on the same = client as where the kqueue is lurking. >=20 > Otherwise you could run some daemon on the server which pushes the = notifications out of band of the NFS protocol to the clients. Which = probably gives interesting results together with the caching of the NFS = client. But that is another story we see at work. (postfix -> you have = mail! -> NFS -> imap -> no you don't -> O yes, you have. :-) ) >=20 in my case it was a python app (flask restful) that when run in debug = mode would restart if some file changed, but some days ago that stopped working, Since I had updated the kernel = and the ports it took me some time to find out what had happened, it had nothing to do with the upgrades = but instead I had installed =E2=80=98watchdog.py=E2=80=99 which flaks->werkseig->reload decided to use :-( =20 rabbit hole indeed. thanks, danny > Regards, > Ronald. >=20 > Van: Daniel Braniss <danny@cs.huji.ac.il> > Datum: woensdag, 11 november 2020 09:40 > Aan: stable@freebsd.org > Onderwerp: kqueue and NFS >> Hi, >> I have a vague recollection that kqueue does not work for NFS files, >> any chance that this will be made possible? >> cheers, >> danny >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?634878874.26.1605091510541>