Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Mar 2015 12:55:52 -0600
From:      Kim Shrier <kim@westryn.net>
To:        Jordan Hubbard <jkh@mail.turbofuzz.com>
Cc:        FreeBSD Hackers <freebsd-hackers@freebsd.org>, "O'Connor, Daniel" <darius@dons.net.au>, Guy Helmer <guy.helmer@gmail.com>
Subject:   Re: file system change notifications
Message-ID:  <CF509EC7-52B4-480E-82E8-FB5173CE0524@westryn.net>
In-Reply-To: <85EE0305-5D79-4C66-A6F4-05219655DAD5@mail.turbofuzz.com>
References:  <C4BD68D4-0570-4731-AFA2-CDD4DD5490E5@westryn.net> <237A50A5-FAB7-4FC1-B8F1-0E40DCBF6137@dons.net.au> <5786089D-414D-485C-B675-35B5A62C5950@gmail.com> <85EE0305-5D79-4C66-A6F4-05219655DAD5@mail.turbofuzz.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 12, 2015, at 10:24 AM, Jordan Hubbard <jkh@mail.turbofuzz.com> =
wrote:
>=20
>=20
>> On Mar 12, 2015, at 6:37 AM, Guy Helmer <guy.helmer@gmail.com> wrote:
>>=20
>> How are Darwin (OS X) fsevents implemented? It=E2=80=99s a been a =
handy interface for some of my work.
>=20
> They have their own tap from the kernel and their own daemon =
(fseventsd) to handle coalescing and a publish/subscribe model that will =
feed multiple consumers without duplicating or losing events (I =
haven=E2=80=99t looked deeply into the implementation, but presumably =
all the cache management is there as well so that memory consumption can =
be kept manageable.
>=20
> Maybe someone should keep a list of =E2=80=9COS X features we would =
really like in FreeBSD=E2=80=9D (add purgeable memory and memory =
pressure bands to that list while you=E2=80=99re at it) and parcel them =
out as GSoC projects. :-)
>=20
> - Jordan

I was curious if the OS X code, which I believe adds some functionality =
to VFS along with fseventd for actually handling the notifications, =
would be a good model for FreeBSD.  I need to study the OS X code some =
more to make sure I understand it.

Also, to clarify, I am not proposing this as a GSoC project.  I was just =
referring to a GSoC project that seemed to address this problem.  If I =
can figure out a good approach for adding this to FreeBSD, I would do it =
myself.

Kim




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CF509EC7-52B4-480E-82E8-FB5173CE0524>