From: Junio C Hamano <gitster@pobox.com>
To: Chris Torek <chris.torek@gmail.com>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH] t5512.40 sometimes dies by SIGPIPE
Date: Sun, 15 Sep 2024 09:13:12 -0700 [thread overview]
Message-ID: <xmqq5xqwsxnr.fsf@gitster.g> (raw)
In-Reply-To: <CAPx1GvePRNzt_LFJAf+_-abdt--075LG8-DA=2YW_0R1soXz_w@mail.gmail.com> (Chris Torek's message of "Sat, 14 Sep 2024 16:27:50 -0700")
Chris Torek <chris.torek@gmail.com> writes:
> It's more complicated than that (and varies on MacOS), but it's true
> that the Go runtime wraps all OS-level write() operations. The reason
> for that is that Go has its own internal "thread" (g/m/p things, really)
> scheduler and does *all* I/O as non-blocking calls. Anything that
> potentially blocks an actual OS-level thread has to be handled
> specially. It's quite messy and You Don't Want To Go There (no
> pun intended) if you don't have to.
That sounds like a fun hack ;-)
prev parent reply other threads:[~2024-09-15 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 19:26 [PATCH] t5512.40 sometimes dies by SIGPIPE Junio C Hamano
2024-09-13 19:44 ` Eric Sunshine
2024-09-13 20:48 ` Junio C Hamano
2024-09-14 6:41 ` Jeff King
2024-09-14 17:09 ` Junio C Hamano
2024-09-16 8:07 ` Patrick Steinhardt
2024-09-14 23:27 ` Chris Torek
2024-09-15 16:13 ` Junio C Hamano [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=xmqq5xqwsxnr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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