Re: minimum write size of SOCK_STREAM?

To: RVP <rvp%sdf.org@localhost>
Subject: Re: minimum write size of SOCK_STREAM?
From: Andrew Cagney <andrew.cagney%gmail.com@localhost>
Date: Sat, 1 Nov 2025 10:54:28 -0400

On 2025年10月31日 at 20:08, RVP <rvp%sdf.org@localhost> wrote:
>
> On 2025年10月31日, Andrew Cagney wrote:
>
> >> With SOCK_STREAM, partial reads can always happen. If you want whole-packet
> >> reads (< MTU size) you'll have to use SOCK_DGRAM or SOCK_SEQPACKET; or send
> >> the message size too, so that the server can loop until it gets the whole
> >> packet.
> >
> > yea, might be time to update to SOCK_SEQPACKET
> >
>
> If you want to keep using SOCK_STREAM, then see: sendmsg(2), CMSG_DATA(3) and
> recvmsg(2) (w/ MSG_WAITALL).
I just want the code to work, portably :-)
I've switched to AF_UNIX+SOCK_SEQPACKET, thanks.
Andrew

References:
- minimum write size of SOCK_STREAM?
  - From: Andrew Cagney
- Re: minimum write size of SOCK_STREAM?
  - From: RVP
- Re: minimum write size of SOCK_STREAM?
  - From: Andrew Cagney
- Re: minimum write size of SOCK_STREAM?
  - From: RVP

Prev by Date: Re: compat_linux failures due to execve, openat, etc.
Next by Date: Re: compat_linux failures due to execve, openat, etc.
Previous by Thread: Re: minimum write size of SOCK_STREAM?
Next by Thread: way to restore "bootx64.efi"
Indexes:

Home | Main Index | Thread Index | Old Index