From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30544 invoked from network); 12 Oct 2020 16:42:09 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 12 Oct 2020 16:42:09 -0000 Received: (qmail 22234 invoked by uid 550); 12 Oct 2020 16:40:03 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 30160 invoked from network); 12 Oct 2020 16:30:49 -0000 Date: Mon, 12 Oct 2020 19:30:31 +0300 From: Jouni Roivas To: Rich Felker CC: Message-ID: <20201012163031.GA2950028@tuxera.com> References: <20201012125901.2629590-1-jouni.roivas@tuxera.com> <20201012150215.GH17637@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20201012150215.GH17637@brightrain.aerifal.cx> X-Originating-IP: [87.92.44.32] X-ClientProxiedBy: tuxera-exch.ad.tuxera.com (10.20.48.11) To tuxera-exch.ad.tuxera.com (10.20.48.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235,18.0.687 definitions=2020-10-12_12:2020-10-12,2020-10-12 signatures=0 X-Proofpoint-Spam-Details: rule=mpy_notspam policy=mpy score=0 spamscore=0 bulkscore=0 mlxlogscore=854 adultscore=0 suspectscore=1 mlxscore=0 phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2010120129 Subject: Re: [musl] [PATCH] Skip writing first iovec if it's empty The 10/12/2020 11:02, Rich Felker wrote: > Note that commit e7eeeb9f2a4a358fb0bbed81e145ef5538ff60f0 did the > analog for __stdio_read in a way that's probably slightly better, but > that would need adaptation to work for the write case. Thanks for pointing out that commit. For read case that looks indeed better, but for the write case I'll keep my implementation for the simplicity. However I think I take and adapt the commit message from the read case. -- Jouni