user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: Re: [PATCH] {dir,inbox}idle: use level-triggered epoll
Date: Mon, 4 Oct 2021 06:55:36 -0300	[thread overview]
Message-ID: <YVrPmLitJv06uhon@dcvr> (raw)
In-Reply-To: <>

Eric Wong <> wrote:
> Both read(2) on inotify and kevent(2) have a finite amount of

    events.  Let the kernel notify us again in cases where we'd
    need to retry instead of looping ourselves.

My brain is still experiencing packet loss :x

      reply	other threads:[~2021-10-04  9:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04  8:26 Eric Wong
2021-10-04  9:55 ` Eric Wong [this message]

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YVrPmLitJv06uhon@dcvr \ \ \
    --subject='Re: [PATCH] {dir,inbox}idle: use level-triggered epoll' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).