From: Chris Brannon <chris@the-brannons.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: public-inbox-convert hangs on systems using musl libc
Date: Wed, 21 Dec 2022 12:46:44 -0800 [thread overview]
Message-ID: <87mt7glc23.fsf@the-brannons.com> (raw)
In-Reply-To: <20221221194855.GA5179@dcvr> (Eric Wong's message of "Wed, 21 Dec 2022 19:48:55 +0000")
Eric Wong <e@80x24.org> writes:
> Are you able to isolate whether $PIPE_BUFSIZ or MAX_INFLIGHT on
> it's own fixes it?
MAX_INFLIGHT is sufficient. In fact, $PIPE_BUFSIZ had no effect at all
when I tried just now.
> And can you confirm the ->blocking(0) change had no effect on
> it's own?
That was the first thing I tried, and it had no effect.
> Capping MAX_INFLIGHT to a smaller value is probably fine (maybe
> 10 can work).
I tried with 10 just now, and that was fine also.
> I also do wonder if you've hit a kernel bug under low memory
> conditions. I've certainly encountered problems with TCP
> traffic hanging processes due to memory compaction.
I doubt it. I looked during a deadlock, and I had 2.66 GiB available.
-- Chris
next prev parent reply other threads:[~2022-12-21 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 11:28 public-inbox-convert hangs on systems using musl libc Chris Brannon
2022-12-21 12:21 ` Eric Wong
2022-12-21 13:46 ` Chris Brannon
2022-12-21 19:48 ` Eric Wong
2022-12-21 20:46 ` Chris Brannon [this message]
2022-12-21 21:11 ` Eric Wong
2022-12-21 22:17 ` Chris Brannon
2022-12-21 23:22 ` [PATCH] git: cap MAX_INFLIGHT value to POSIX minimum Eric Wong
2022-12-21 23:57 ` Chris Brannon
2023-01-04 3:49 ` [PATCH] git: fix asynchronous batching for deep pipelines Eric Wong
2023-01-05 1:08 ` Chris Brannon
2023-01-05 1:44 ` [PATCH] git: write_all: remove leftover debug messages Eric Wong
2023-01-05 7:32 ` Chris Brannon
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mt7glc23.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.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).