From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [WIP v2 0/4] sleepy GC
Date: Tue, 1 May 2018 08:08:40 +0000 [thread overview]
Message-ID: <20180501080844.22751-1-e@80x24.org> (raw)
The following changes since commit 41f4ac6aa21588722a6323dbbc34274b7e9aec49:
ast.c: use enum in switch for warnings (2018-05-01 06:55:43 +0000)
are available in the Git repository at:
git://80x24.org/ruby.git sleepy-gc-v2
for you to fetch changes up to 9d1609d318821b11614da6f952acadf7d3a3e083:
thread.c: native_sleep callers may perform GC (2018-05-01 07:57:21 +0000)
v2 updates:
- [PATCH 2/4] uses correct functions for incremental work
- [PATCH 3/4] accounts for select(2) clobbering its timeval arg
- [PATCH 4/4] totally redone; native_sleep callers are all rather
complex and it can be improved in future patches
----------------------------------------------------------------
Eric Wong (4):
thread.c (timeout_prepare): common function
gc: rb_wait_for_single_fd performs GC if idle (Linux)
thread.c (do_select): perform GC if idle
thread.c: native_sleep callers may perform GC
gc.c | 30 +++++++++
internal.h | 4 ++
thread.c | 197 +++++++++++++++++++++++++++++++++++++------------------
thread_pthread.c | 6 ++
thread_sync.c | 21 +++++-
thread_win32.c | 6 ++
6 files changed, 197 insertions(+), 67 deletions(-)
next reply other threads:[~2018-05-01 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 8:08 Eric Wong [this message]
2018-05-01 8:08 ` [WIP v2 1/4] thread.c (timeout_prepare): common function Eric Wong
2018-05-01 8:08 ` [WIP v2 2/4] gc: rb_wait_for_single_fd performs GC if idle (Linux) Eric Wong
2018-05-01 8:08 ` [WIP v2 3/4] thread.c (do_select): perform GC if idle Eric Wong
2018-05-01 8:08 ` [WIP v2 4/4] thread.c: native_sleep callers may perform GC Eric Wong
2018-05-02 4:42 ` [PATCH 5/4] thread_sync.c (mutex_lock): add missing else Eric Wong
2018-05-02 4:52 ` [PATCH 6/4] gc.c: allow disabling sleepy GC Eric Wong
2018-05-02 4:57 ` [PATCH] benchmark: add benchmarks for " 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=20180501080844.22751-1-e@80x24.org \
--to=e@80x24.org \
--cc=spew@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.
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).