unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 24756-done@debbugs.gnu.org
Subject: bug#24756: 26.0.50; Emacs should not use pselect
Date: Sun, 29 Sep 2019 06:02:56 +0200	[thread overview]
Message-ID: <CADwFkmntmZLzibXpRaBDMqfnOs4BRkAQd2zYNVQctUKGUH5K5A@mail.gmail.com> (raw)
In-Reply-To: <wvr48tthu2u6.fsf@a.muc.corp.google.com>

Philipp Stephani <p.stephani2@gmail.com> writes:

> Philipp Stephani <p.stephani2@gmail.com> schrieb am Fr., 21. Okt. 2016 um 17:42 Uhr:
>
>  Emacs uses pselect for IO multiplexing, limiting the number of available
>  file descriptors to FD_SETSIZE.  Rather, epoll/kqueue should be used, if
>  available.
>
> Some good counter-arguments were brought up:
> - pselect is in the POSIX standard, whereas the possible replacements (ppoll/epoll/kqueue) are not.
> - The file descriptor limit should only be hit in pathological cases, e.g. when leaking background processes, and is only a symptom of a bug somewhere else. A higher FD limit would only hide the symptom, but not fix the underlying root cause.
>
> Given that, I'm no longer convinced that switching away from pselect would be a good idea (but I'll leave this bug open for now to provide a space for discussion).

That was three years ago, and no such discussion has taken place here.
If there is a continued need to discuss this, perhaps it's better to
take it to emacs-devel.  I'm therefore closing this bug report.

If anyone disagrees, they should feel free to reopen.

Best regards,
Stefan Kangas





      parent reply	other threads:[~2019-09-29  4:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 15:41 bug#24756: 26.0.50; Emacs should not use pselect Philipp Stephani
2016-10-25 11:45 ` Philipp Stephani
2019-09-29  4:02 ` Stefan Kangas [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:
  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=CADwFkmntmZLzibXpRaBDMqfnOs4BRkAQd2zYNVQctUKGUH5K5A@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=24756-done@debbugs.gnu.org \
    --cc=p.stephani2@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.
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).