From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-developers@cygwin.com
Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot
Date: Sun, 7 Nov 2021 12:46:06 +0900 [thread overview]
Message-ID: <20211107124606.f68b27d7e5600b203e37fc7a@nifty.ne.jp> (raw)
In-Reply-To: <5819b4c3-ea10-8292-2449-23d79e6bc896@cornell.edu>
On Sat, 6 Nov 2021 12:38:43 -0400
Ken Brown wrote:
> On 11/6/2021 7:42 AM, Corinna Vinschen wrote:
> > On Nov 6 15:10, Takashi Yano wrote:
> >> Ken Brown wrote:
> >>> On 11/5/2021 3:41 PM, Takashi Yano via Cygwin wrote:
> >>>> What about setting pipe mode to byte by default?
> >>>
> >>> I have a vague recollection that this caused some other problem, but I'll have
> >>> to review the email discussions from a few months ago. I'm traveling at the
> >>> moment and won't get to this for a few days.
>
> I found it:
>
> https://cygwin.com/pipermail/cygwin-developers/2021-August/012219.html
Thanks!
I tested the current pipe behaviour using the following test code.
With both message and byte pipe, the result are the same:
w:65536
r:2048
w:-1
which complies with POSIX requirement.
I have tested under Windows Vista, 7 and 10 and got same results.
#include <unistd.h>
#include <stdio.h>
#include <limits.h>
#include <fcntl.h>
#define PIPE_SIZE 65536
int main()
{
int fd[2];
char buf[PIPE_SIZE];
int flags;
pipe(fd);
/* Set non-blocking */
flags = fcntl(fd[1], F_GETFL);
flags |= O_NONBLOCK;
fcntl(fd[1], F_SETFL, flags);
/* Fill pipe */
printf("w:%d\n", write(fd[1], buf, PIPE_SIZE));
/* Free PIPE_BUF/2 bytes */
printf("r:%d\n", read(fd[0], buf, PIPE_BUF/2));
/* Write PIPE_BUF bytes */
printf("w:%d\n", write(fd[1], buf, PIPE_BUF));
return 0;
}
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-11-07 3:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEv6GOB8PXHgHoz7hdJy6Bia2GWEmUDnTd252gTGinz2vuv=hA@mail.gmail.com>
[not found] ` <20211105123950.b118a7f2ba38379764df4c12@nifty.ne.jp>
[not found] ` <CAEv6GOA-y58YrftXgEgFrjqtOTHmfdu2Vrq76Lwn0suZpZ=U9w@mail.gmail.com>
[not found] ` <20211105170542.96ce6dd4ca32880ddfddd660@nifty.ne.jp>
[not found] ` <CAEv6GODiM88Xfhk9R3AcEW6UTYSzACzYe4C0gPoTYm=u9ZTqRQ@mail.gmail.com>
[not found] ` <20211106044116.698b465a5d8ed6ce2cc75c99@nifty.ne.jp>
[not found] ` <2cfa5de7-3b95-9062-4572-f36d304bc916@cornell.edu>
2021-11-06 6:10 ` Takashi Yano
2021-11-06 11:42 ` Corinna Vinschen
2021-11-06 12:02 ` Corinna Vinschen
2021-11-06 14:13 ` Takashi Yano
2021-11-06 17:20 ` Corinna Vinschen
2021-11-07 3:01 ` Takashi Yano
2021-11-06 16:38 ` Ken Brown
2021-11-06 17:20 ` Corinna Vinschen
2021-11-07 3:46 ` Takashi Yano [this message]
2021-11-07 22:20 ` Ken Brown
2021-11-08 8:23 ` Takashi Yano
2021-11-08 9:46 ` Corinna Vinschen
2021-11-10 8:30 ` Takashi Yano
2021-11-10 10:34 ` Corinna Vinschen
2021-11-10 13:30 ` Takashi Yano
2021-11-10 20:35 ` Corinna Vinschen
2021-11-10 21:32 ` Ken Brown
2021-11-11 16:11 ` Ken Brown
2021-11-12 8:38 ` Takashi Yano
2021-11-16 23:46 ` Takashi Yano
2021-11-17 8:10 ` Takashi Yano
2021-11-17 15:12 ` Ken Brown
2021-11-11 9:52 ` Corinna Vinschen
2021-11-11 11:12 ` Takashi Yano
2021-11-11 11:33 ` Corinna Vinschen
2021-11-11 12:02 ` Takashi Yano
2021-11-11 13:20 ` Takashi Yano
2021-11-11 16:07 ` Corinna Vinschen
2021-11-12 8:33 ` Takashi Yano
2021-11-12 10:02 ` Corinna Vinschen
2021-12-12 13:26 ` Takashi Yano
2021-12-12 13:36 ` Ken Brown
2021-12-13 11:15 ` Takashi Yano
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=20211107124606.f68b27d7e5600b203e37fc7a@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-developers@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).