From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.135]) by sourceware.org (Postfix) with ESMTPS id 713653858D34 for ; Mon, 30 Aug 2021 08:48:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 713653858D34 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=cygwin.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=cygwin.com Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MqbDs-1mpJ190kWu-00meyp for ; Mon, 30 Aug 2021 10:48:43 +0200 Received: by calimero.vinschen.de (Postfix, from userid 500) id A9806A80D72; Mon, 30 Aug 2021 10:48:42 +0200 (CEST) Date: Mon, 30 Aug 2021 10:48:42 +0200 From: Corinna Vinschen To: cygwin-developers@cygwin.com Subject: Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled? Message-ID: Reply-To: cygwin-developers@cygwin.com Mail-Followup-To: cygwin-developers@cygwin.com References: <3b560051-ab27-f392-ca4b-d1fd9b5733b0@cornell.edu> <20210827202440.47706fc2fc07c5e9a1bc0047@nifty.ne.jp> <4f2cb5f3-ce9c-c617-f65f-841a5eca096e@cornell.edu> <20210828022111.91ef5b4ff24f6da9fadb489e@nifty.ne.jp> <20210828184102.f2206a8a9e5fe5cf24bf5e45@nifty.ne.jp> <20210829180729.48b4e877f773cb3980c5766d@nifty.ne.jp> <789f056a-f164-d71d-1dc9-230f5a41846d@cornell.edu> <20210830043756.8aa0ada77db0bfbbe3889f62@nifty.ne.jp> <47e5dd74-b940-f305-fd5a-c6c9d8f41305@cornell.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <47e5dd74-b940-f305-fd5a-c6c9d8f41305@cornell.edu> X-Provags-ID: V03:K1:uKl6uuAO+oNN3jYlzZwAGICbhOnXjabSc3eRj9B1OASQ5x/L6XQ jI5P2JVemHbaM6j0PXc8hdG8VN9pgvpflNAxZQZNpeKcUT+lcALP3FDRfenTc81rBsQJNlo oWxwUbbVz4pM89zdUjQQRDaR5nSR3BeJRbBjT2BGEkXFWHGa4HyVgGheUNdpVAy5ymrJv/5 Qu4Tw91349QXbk6W+mCzg== X-UI-Out-Filterresults: notjunk:1;V03:K0:xYbLe+aDOtA=:ERwWvR6gMVp8uXkVsZoNKG 4dJYgjiKRbNY5NWY0bfkxapWgWqwLz6W9/lTskOTd0BIe8uc7ouEaMQAYEREfuEeZaKAjUuo6 Wx45xQsXq+K57awBC91TxnQ4ZSb2wf5i5c6Yy2qY1VHBGDdZmQjv/7kvhfCIfFbbHdiiU4voD WRtSx658klSyw7kjr+kDtVH8ufTx0YYp8oFzX17i14uX1MH7HF0Dc5xbftt0gW10ehBXEgW/w S38u4qKxhqZtHAvd4CF7ahHSVWRCWt1cmzMI1CXLEKaKIj5FTDSra2mx5vvF7idYUjpYyoKar Dyo39fAaL0IDpm0zrL5OGuF9lu3p7+CLDZZUqmPIibfuQ8l5y7HSxkFhuG42lopajk478fNdI xTNfqgxv80+yeNmT+gVTZBJC+8Ol8HPEHihwitX8I7RVX2C1+1ozFjGpB5+f6UNwOlvGc1CUR tTRXBM5/9N32QBdv6R0fqY/96i4Se7cR0cW4k8dLZ3JsNX/eavTLIRiBs2LUcTnkwazVCcqND +z8YIB7MfvWVrVE7wYRr6bkc9VGtORbs3teCbdzBkXhoKiU72WzcPQ6IoOchkvg4+/ZBjIc/e IHozLRdCbZQku6LfWPalFrNVD9yi1qmkAPUkAf1HPMJqgvOqakXskvKfGO5jjB8lQigc7HnIE MAuXxuBkrdhZrHSgW7h4MKlt4MA8S10ss69qT/5Vp8Oc1ghlS/Dy6n9EtDDAAM180suwIJTKw kgnd0SpiCLfWNr/4uLeGVDjrXRhnZbvQ4AqD1D5ly9Nr7+7Hxb1S/vDOwGg= X-Spam-Status: No, score=-100.0 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_NONE, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NEUTRAL, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-developers@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin core component developers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2021 08:48:55 -0000 [Moved to cygwin-developers] On Aug 29 17:09, Ken Brown via Cygwin wrote: > On 8/29/2021 3:37 PM, Takashi Yano wrote: > > Only the small thing remaining is pipe mode. If the pipe mode > > is changed to byte mode, the following issue will be solved. > > https://cygwin.com/pipermail/cygwin/2021-March/247987.html > > > > How about the simple patch attached? > > > > The comment in pipe code says: > > Note that the write side of the pipe is opened as PIPE_TYPE_MESSAGE. > > This *seems* to more closely mimic Linux pipe behavior and is > > definitely required for pty handling since fhandler_pty_master > > writes to the pipe in chunks, terminated by newline when CANON mode > > is specified. > > > > This mentions about pty behaiviour in canonical mode, however, the > > pty pipe is created as message mode even with this patch. Are there > > any other reasons that message mode is preferred for pipe? > > No idea. All I remember is that there was a lot of discussion around the > time that it was decided to use PIPE_TYPE_MESSAGE by default. Corinna > probably remembers the reasons. No, sorry, I don't remember the exact discussion. But it seemed to fix quite a few issues at the time. Corinna