From: "Perry E. Metzger" <perry@piermont.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: emacs-devel@gnu.org
Subject: Re: gfile-based file notifications are not immediate
Date: Sun, 2 Nov 2014 10:50:59 -0500 [thread overview]
Message-ID: <20141102105059.6522c39d@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <CAM-tV-_6_FU556VyxQf-jEdbCmsJR1ZnVo9vihON_tQbFLyr=Q@mail.gmail.com>
On Sun, 2 Nov 2014 09:15:32 -0500 Noam Postavsky
<npostavs@users.sourceforge.net> wrote:
> On Fri, Oct 31, 2014 at 5:28 PM, Perry E. Metzger
> <perry@piermont.com> wrote:
> > On Thu, 30 Oct 2014 21:32:30 +0100 Rüdiger Sonderfeld
> > <ruediger@c-plusplus.de> wrote:
> >> Glib already seems to use several hacks to work around the
> >> limitations of kqueue
> >
> > As a aside: people keep mentioning that they believe kqueue has
> > some sort of fundamental limitations. I'm curious what those are
> > perceived to be. So far as I can tell, the interface is fine --
> > it is a rough equivalent to what you can do in Linux with epoll
> > (which is currently preferred over select and its successors).
>
> I don't know the details, but I gathered the limitations are
> relative to *inotify*. Presumably epoll would also be a poor
> substitute for inotify, which is why Linux has both.
>
epoll and inotify are orthogonal. epoll says when a file descriptor
has data on it. inotify provides a file descriptor that yields event
information for file changes.
kqueue implements features of both select/poll and inotify. I'm not
sure what limitations kqueue might have vs. inotify, but they are
unlikely to be significant in this context.
Perry
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2014-11-02 15:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 20:17 gfile-based file notifications are not immediate Dima Kogan
2014-10-26 7:55 ` Michael Albinus
2014-10-26 13:12 ` Ken Brown
2014-10-28 21:33 ` Rüdiger Sonderfeld
2014-10-29 1:06 ` Stefan Monnier
2014-10-29 2:23 ` Dima Kogan
2014-10-29 3:54 ` Stefan Monnier
2014-10-29 12:03 ` Michael Albinus
2014-10-29 13:56 ` Stefan Monnier
2014-10-29 14:11 ` Óscar Fuentes
2014-10-29 15:29 ` Stefan Monnier
2014-10-29 16:28 ` Michael Albinus
2014-10-29 20:34 ` Stefan Monnier
2014-10-30 15:16 ` Perry E. Metzger
2014-10-30 16:51 ` Stefan Monnier
2014-10-30 17:10 ` Perry E. Metzger
2014-10-30 17:40 ` Michael Albinus
2014-10-30 18:04 ` Perry E. Metzger
2014-10-30 18:06 ` Stefan Monnier
2014-10-30 18:11 ` Michael Albinus
2014-10-30 19:21 ` Perry E. Metzger
2014-10-30 19:39 ` Dima Kogan
2014-10-30 19:27 ` Stefan Monnier
2014-10-29 14:00 ` Wolfgang Jenkner
2014-10-30 19:12 ` Wolfgang Jenkner
2014-10-30 20:32 ` Rüdiger Sonderfeld
2014-10-31 21:28 ` Perry E. Metzger
2014-11-02 14:15 ` Noam Postavsky
2014-11-02 15:50 ` Perry E. Metzger [this message]
2014-10-26 16:02 ` Eli Zaretskii
2014-10-26 17:07 ` Dima Kogan
2014-10-26 17:14 ` Eli Zaretskii
2014-10-26 16:41 ` Michael Albinus
2014-10-28 0:32 ` Dima Kogan
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141102105059.6522c39d@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=emacs-devel@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).