Git development
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: rsbecker@nexbridge.com, Patrick Steinhardt <ps@pks.im>,
	git@vger.kernel.org
Subject: Re: Re* 2.54.0-rc1 NO_WRITEV=Nope  does not work
Date: Thu, 9 Apr 2026 18:21:31 -0400	[thread overview]
Message-ID: <20260409222131.GA3130242@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqmrzbreav.fsf_-_@gitster.g>

On Thu, Apr 09, 2026 at 02:53:28PM -0700, Junio C Hamano wrote:

> > Yuck. I think for 2.54 we either have to truly implement MAX_IO_SIZE
> > support, or we have to revert the use of writev() in send_sideband()
> > until we do.
> 
> Sigh again.

Yeah, I feel the same way. :(

I would be happy if somebody could prove me wrong, though.

> $ git log -Swritev --oneline 8023abc632^..
> 89152af176 cmake: use writev(3p) wrapper as needed
> 26986f4cba sideband: use writev(3p) to send pktlines
> 1970fcef93 wrapper: introduce writev(3p) wrappers
> 3b9b2c2a29 compat/posix: introduce writev(3p) wrapper
> 
> Reverting them gave us the following patch relative to the tip of
> 'master'.

If we are planning to improve the topic post-release (and I think that
is a good idea), then we can do a much smaller revert. If we just revert
26986f4cba (sideband: use writev(3p) to send pktlines, 2026-03-13), then
nobody calls writev (neither the real one nor our fallback). The
wrappers are dead code until we bring it back, but it may make things
easier for fixing post-2.54.

-Peff

  reply	other threads:[~2026-04-09 22:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 19:48 2.54.0-rc1 NO_WRITEV=Nope does not work rsbecker
2026-04-09 21:10 ` Jeff King
2026-04-09 21:53   ` Re* " Junio C Hamano
2026-04-09 22:21     ` Jeff King [this message]
2026-04-09 22:31       ` Junio C Hamano
2026-04-10  4:57         ` Patrick Steinhardt

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=20260409222131.GA3130242@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox