From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) by sourceware.org (Postfix) with ESMTPS id A99A43858D1E for ; Tue, 4 Apr 2023 11:25:07 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A99A43858D1E Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-lj1-x233.google.com with SMTP id x20so33407910ljq.9 for ; Tue, 04 Apr 2023 04:25:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680607506; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=TaKXWQDuLh7IqedyS1Pn3o5KLUUMTZMkk6V0kUVbdm8=; b=izZmivvgD8S+57CZNxxVQ4XqckT1kSSXRSopvLmvvtu4+BzoltolywM6e+2RL38Ltq 0UorN8qNXpNhkXAE4OzMf7Mr02Ea3qY5BE6sZm6VN3Z/gue1cTIBpU0MkVHTInO52CSN fZeM93sWsAlMvHpJQV55G23PhNOT/85M6h8K1MLix4qWEZ1Y6xHZk0WUzHz8ycIMqMXp PU70fyelwEXaK6lI1OsIF/uZAU4DLtU/F/Ff7ohmpgjDfVQY6kZ+12hO99iQDnmYb23G VY6DpB+eye5eP2fpIYQ3UKsnBRG/bkjia7I0Q9xERBy/7XldFNum2B6NVIGArdHkuh4j qMRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680607506; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=TaKXWQDuLh7IqedyS1Pn3o5KLUUMTZMkk6V0kUVbdm8=; b=C2Ln2Ms2kEhJ74RyxavD+8UacUtIeJ3hd4tOJfwiloK77vaJDV9+dDwkwLCi+3alnK XkenY5RGHT/aufiGUvzdy/Cp7+ElDJB3QVr5eExwUGtoqhHo68wEtoDtTv0bhNA5/577 xGPWgeOLohsJrRfu6K80i3U/ukWl2ITUkGAPBJ5v14aAY0+vW25rz+q2lBillYJnag1m PpD1tWDpHyqSRkeK3LLPYtBvA35Qu8iJt7t/fVGTATF2p6Vt8xbFmdRpZkJydcg8OMLH 7AFGGGOFZlk8LF0B5K0FCP0o7xXc97wQtbiwVaXE9Tj+mZforuq105916jWYQDN4dl2h 6WyA== X-Gm-Message-State: AAQBX9fg51A6FzeF87jFExPLTH3mPx3xFjaSogHhyVZjzc60kRVIIH+6 bhor4uEYOW3fPGBAwusObdQ5csWuKPBDDwlvZgKkuBi5rRE= X-Google-Smtp-Source: AKy350bysHdutzZXhddb9jHuiJJkUj39yCnh1VZSf0wkGZcMvSTmjFtLkl1xH2LLjpYix2RMRPDLSwoLXu/JvOIoHg0= X-Received: by 2002:a2e:824a:0:b0:299:b5e6:4c45 with SMTP id j10-20020a2e824a000000b00299b5e64c45mr895108ljh.5.1680607505794; Tue, 04 Apr 2023 04:25:05 -0700 (PDT) MIME-Version: 1.0 References: <62f59e2a-8360-e4a5-1460-3d0de5331fd8@Shaw.ca> In-Reply-To: <62f59e2a-8360-e4a5-1460-3d0de5331fd8@Shaw.ca> From: Chance Date: Tue, 4 Apr 2023 06:24:55 -0500 Message-ID: Subject: Re: MSG_MORE socket.h flag To: cygwin@cygwin.com Content-Type: multipart/alternative; boundary="00000000000063c9aa05f880edaf" X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --00000000000063c9aa05f880edaf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On 2023-04-03 04:56, Corinna Vinschen via Cygwin wrote: > On Apr 2 00:19, Chance via Cygwin wrote: >> I've used cygwin in the past few years using the MSG_MORE flag when using >> some socket functions > > I have no idea how you did that. MSG_MORE was never actually supported > by Cygwin, and the (more or less) equivalent MSG_PARTIAL flag was never > exposed into Cygwin user space. > >> but now it's not defined in cygwin\socket.h and > > It never was! I checked the history back until the year 2000. > >> MSG_EOR is using the value of MSG_MORE (0x8000). Above that in the socket.h >> file there is a comment /* MSG_EOR is not supported. We use the >> MSG_PARTIAL flag here */. I understand this as meaning MSG_EOR now works as >> MSG_MORE would and that MSG_EOR is not usable. Just want some clarification >> on this. > > It just means we're using the bit value of MSG_PARTIAL to expose > a MSG_EOR flag into user space. It was introduced in 2019 because > of POSIX header file compatibility, but it's unsupported and always > results in sedn/recv returning EOPNOTSUPP. > > I'm still puzzled where you got the MSG_MORE definition from, though Ah yes, my memory was foggy, but I've recalled now that I did some work with sockets on a Linux system and had to change this flag in my own source code when I would work on a cygwin platform. It's been a while; sorry for the confusement! On Mon, Apr 3, 2023 at 11:05=E2=80=AFAM Brian Inglis = wrote: > On 2023-04-03 04:56, Corinna Vinschen via Cygwin wrote: > > On Apr 2 00:19, Chance via Cygwin wrote: > >> I've used cygwin in the past few years using the MSG_MORE flag when > using > >> some socket functions > > > > I have no idea how you did that. MSG_MORE was never actually supported > > by Cygwin, and the (more or less) equivalent MSG_PARTIAL flag was never > > exposed into Cygwin user space. > > > >> but now it's not defined in cygwin\socket.h and > > > > It never was! I checked the history back until the year 2000. > > > >> MSG_EOR is using the value of MSG_MORE (0x8000). Above that in the > socket.h > >> file there is a comment /* MSG_EOR is not supported. We use the > >> MSG_PARTIAL flag here */. I understand this as meaning MSG_EOR now > works as > >> MSG_MORE would and that MSG_EOR is not usable. Just want some > clarification > >> on this. > > > > It just means we're using the bit value of MSG_PARTIAL to expose > > a MSG_EOR flag into user space. It was introduced in 2019 because > > of POSIX header file compatibility, but it's unsupported and always > > results in sedn/recv returning EOPNOTSUPP. > > > > I'm still puzzled where you got the MSG_MORE definition from, though. > > Not on BSD likely Linux: > > https://github.com/torvalds/linux/blob/master/include/linux/socket.h#L298 > > check for symlinks on poster's system? > > -- > Take care. Thanks, Brian Inglis Calgary, Alberta, Canada > > La perfection est atteinte Perfection is achieved > non pas lorsqu'il n'y a plus rien =C3=A0 ajouter not when there is no mo= re to > add > mais lorsqu'il n'y a plus rien =C3=A0 retirer but when there is no mo= re to > cut > -- Antoine de Saint-Exup=C3=A9ry > --00000000000063c9aa05f880edaf--