From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: timerfd question
Date: Fri, 12 Nov 2021 10:41:10 +0100 [thread overview]
Message-ID: <YY42tq3Ug/qqUCMJ@calimero.vinschen.de> (raw)
In-Reply-To: <02bf0670-ab2f-8bb2-a882-0ef8902bd791@cornell.edu>
On Nov 11 17:52, Ken Brown wrote:
> 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)?
They don't share code, nor threads. I don't see a reason they should
influence each other. Both are starting timers and handle them
in independent threads.
> 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.
A STC might be helpful.
Corinna
prev parent reply other threads:[~2021-11-12 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 22:52 Ken Brown
2021-11-12 9:41 ` Corinna Vinschen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YY42tq3Ug/qqUCMJ@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).