public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugzilla at tecnocode dot co.uk" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/30287] sigevent needs a notification method compatible with poll
Date: Tue, 25 Apr 2023 17:11:20 +0000	[thread overview]
Message-ID: <bug-30287-131-cPbeM8gZaJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30287-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30287

--- Comment #2 from Philip Withnall <bugzilla at tecnocode dot co.uk> ---
I’m not sure how timerfd_create() helps; aiui to fix this, a new event type
would have to be added to the `SIGEV_*` types and supported internally by
sigevent.

In any case, I have worked around this problem in GLib by running the
synchronous getaddrinfo() in a local thread pool, so I am no longer attempting
to use getaddrinfo_a(). It seems like that API has a few too many caveats to
make it useful in my use case.

As such, feel free to close this issue if you think sigevent wouldn’t benefit
from additional API at the moment (I’m not sure how actively it’s used by
anyone). Thanks

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-04-25 17:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 15:54 [Bug libc/30287] New: " bugzilla at tecnocode dot co.uk
2023-04-02 19:16 ` [Bug libc/30287] " fw at deneb dot enyo.de
2023-04-25 17:11 ` bugzilla at tecnocode dot co.uk [this message]
2023-04-25 17:16 ` fweimer at redhat dot com
2023-05-15 14:40 ` bugzilla at tecnocode dot co.uk

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=bug-30287-131-cPbeM8gZaJ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).