From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: "'Han-Wen Nienhuys via GitGitGadget'" <gitgitgadget@gmail.com>,
<git@vger.kernel.org>, "'Han-Wen Nienhuys'" <hanwenn@gmail.com>,
"'Han-Wen Nienhuys'" <hanwen@google.com>
Subject: Re: [PATCH] move sleep_millisec to git-compat-util.h
Date: Wed, 25 Nov 2020 15:12:07 -0800 [thread overview]
Message-ID: <xmqqy2ipav5k.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <018301d6c371$37bf6820$a73e3860$@nexbridge.com> (Randall S. Becker's message of "Wed, 25 Nov 2020 16:23:22 -0500")
"Randall S. Becker" <rsbecker@nexbridge.com> writes:
> I just chatted with my team and we think that sticking with the existing
> poll call is probably better in the long term. We are planning to try to get
> git to work using PUT threads - but that is a longer project for a whole
> slew of reasons. It involves pulling all or most of the FLOSS stuff out, or
> making that configurable to use FLOSS when not using threads and not using
> FLOSS when using threads. It might be useful, however, to use usleep()
> instead of poll(NULL) when threading is used on most platforms as it is a
> more effective way of context switching between threads than select().
Yeah, if usleep() is portable enough, that would probably be the
ideal direction to go.
prev parent reply other threads:[~2020-11-25 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 19:10 [PATCH] move sleep_millisec to git-compat-util.h Han-Wen Nienhuys via GitGitGadget
2020-11-24 21:51 ` Junio C Hamano
2020-11-24 22:12 ` Randall S. Becker
2020-11-25 3:12 ` Junio C Hamano
2020-11-25 21:23 ` Randall S. Becker
2020-11-25 23:12 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy2ipav5k.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hanwen@google.com \
--cc=hanwenn@gmail.com \
--cc=rsbecker@nexbridge.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).