public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-devel <cygwin-developers@cygwin.com>
Subject: timerfd question
Date: Thu, 11 Nov 2021 17:52:48 -0500	[thread overview]
Message-ID: <02bf0670-ab2f-8bb2-a882-0ef8902bd791@cornell.edu> (raw)

This question is almost certainly too vague to be answerable, but I'll try 
anyway.  Is there any obvious reason that it's bad to have two timers running 
simultaneously, one using timerfd (started via timerfd_settime) and one using a 
POSIX timer (started via timer_settime)?

Here's the context: Emacs runs timers.  Until recently it used timerfd if 
available, and otherwise a POSIX timer.  After a recent change, it starts both 
kinds of timers.  This causes a severe slowdown on Cygwin 
(https://debbugs.gnu.org/cgi/bugreport.cgi?bug=51734#32).  The easiest thing is 
just to disable that change on Cygwin, but I'd feel better understanding why 
this is a problem.

Ken

             reply	other threads:[~2021-11-11 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 22:52 Ken Brown [this message]
2021-11-12  9:41 ` Corinna Vinschen

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

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

  git send-email \
    --in-reply-to=02bf0670-ab2f-8bb2-a882-0ef8902bd791@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-developers@cygwin.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.
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).