From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [RFC] wfcqueue: allow defining CDS_WFCQ_WAIT_SLEEP to override `poll'
Date: Mon, 20 Aug 2018 15:48:35 -0400 (EDT) [thread overview]
Message-ID: <421142351.3072.1534794515817.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20180817203134.zhvzvddsdtv54wg5@dcvr>
----- On Aug 17, 2018, at 4:31 PM, Eric Wong normalperson at yhbt.net wrote:
> Mathieu Desnoyers <mathieu.desnoyers at efficios.com> wrote:
>> ----- On Aug 1, 2018, at 2:54 PM, Eric Wong normalperson at yhbt.net wrote:
>>
>> > Users may want to use alternative sleeping behavior instead of
>> > `poll'. Make CDS_WFCQ_WAIT_SLEEP a macro which may be defined
>> > before including wfcqueue.h.
>> >
>> > This alternative behavior could include logging, performing
>> > low-priority cleanup work, sleeping a shorter/longer interval
>> > or any combination of that.
>> >
>> > This will also make integration into glibc easier, as `poll'
>> > linkage causes conformance test failures even when relegated
>> > to an impossible code path:
>> > https://public-inbox.org/libc-alpha/20180801092626.jrwyrojfye4avcis at whir/
>>
>> Rather than introducing a macro here, can we extend the API to
>> pass a callback and a private pointer that would perform the
>> sleeping behavior requested by the caller ?
>
> Given this is deep in the call stack, it would require modifying
> a lot of callers. So it seems like a compatibility/migration
> nightmare. I fear it's too much work for a small improvement.
>
> For glibc, we can simply define `poll' to `__poll' to avoid
> those test failures, at least
I merged the patch you proposed, it makes sense considering the
context.
Thanks!
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2018-08-20 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 18:54 Eric Wong
2018-08-13 14:13 ` Mathieu Desnoyers
2018-08-17 20:31 ` Eric Wong
2018-08-20 19:48 ` Mathieu Desnoyers [this message]
2018-08-20 19:47 ` Mathieu Desnoyers
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=421142351.3072.1534794515817.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.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