From: Eric Wong <e@80x24.org>
To: mwrap-perl@80x24.org
Subject: [PATCH 7/7] README: add some caveats (signalfd usage w/ current URCU)
Date: Mon, 19 Dec 2022 11:19:22 +0000 [thread overview]
Message-ID: <20221219111922.1079128-8-e@80x24.org> (raw)
In-Reply-To: <20221219111922.1079128-1-e@80x24.org>
Fortunately, there aren't a lot of signalfd users right now
(except me :x). In any case, this problem should sort itself
out in a few years when new URCU releases replace old ones.
Also, only the EXTREMELY EXPENSIVE ENTERPRISE EDITION will be
able to support Perl files with over 16.7M lines in them :P
---
README | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/README b/README
index ba95d47..0acbe50 100644
--- a/README
+++ b/README
@@ -61,6 +61,11 @@ malloc locations.
* 32-bit machines are prone to overflow (WONTFIX)
+* signalfd(2)-reliant code will need latest URCU with commit
+ ea3a28a3f71dd02f (Disable signals in URCU background threads, 2022-09-23)
+
+* Perl source files over 16.7 million lines long are not supported :P
+
== Public mail archives (HTTP, Atom feeds, IMAP mailbox, NNTP group):
https://80x24.org/mwrap-perl/
next prev parent reply other threads:[~2022-12-19 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 11:19 [PATCH 0/7] shrinkage Eric Wong
2022-12-19 11:19 ` [PATCH 1/7] core: shrink src_loc 8 bytes on x86-64 Eric Wong
2022-12-19 11:19 ` [PATCH 2/7] core: shrink src_loc by another " Eric Wong
2022-12-19 11:19 ` [PATCH 3/7] core: drop FreeBSD-specific mutex initialization Eric Wong
2022-12-19 11:19 ` [PATCH 4/7] calloc: consolidate ENOMEM handling Eric Wong
2022-12-19 11:19 ` [PATCH 5/7] *alloc: limit scope of RCU lock Eric Wong
2022-12-19 11:19 ` [PATCH 6/7] core: simplify callers of alloc_insert_rcu Eric Wong
2022-12-19 11:19 ` Eric Wong [this message]
2022-12-19 22:57 ` [WIP] attempt to workaround older URCU for signalfd Eric Wong
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=20221219111922.1079128-8-e@80x24.org \
--to=e@80x24.org \
--cc=mwrap-perl@80x24.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mwrap-perl.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).