From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1CB42C433F5 for ; Wed, 18 May 2022 23:37:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231403AbiERXh3 (ORCPT ); Wed, 18 May 2022 19:37:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52280 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231449AbiERXh0 (ORCPT ); Wed, 18 May 2022 19:37:26 -0400 Received: from mx0b-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5373260060 for ; Wed, 18 May 2022 16:37:25 -0700 (PDT) Received: from pps.filterd (m0148460.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 24IN6F8L007726 for ; Wed, 18 May 2022 16:37:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : mime-version : content-transfer-encoding : content-type; s=facebook; bh=IUAVR5Z2N3q1Q5wuTpCYcSVt33XuR3y6zhERgNmypXk=; b=HiVKLhKJgFCqe9PDgIqPxuzAjhWusXR67WsUdu/jAaQOz0WKb6PjkMYYQyt+WThm/VLF Qb65t8KiakDRxmaHvm3vdOEzW0onH9u/Q3gWgYClhKcjdcT7MkMps1a05yGgqH7m66Ke enRT6EhC3ynRoXmY120QChXvHpJ6aqB9WxY= Received: from mail.thefacebook.com ([163.114.132.120]) by mx0a-00082601.pphosted.com (PPS) with ESMTPS id 3g4p9gft8b-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 18 May 2022 16:37:24 -0700 Received: from twshared19572.14.frc2.facebook.com (2620:10d:c085:208::f) by mail.thefacebook.com (2620:10d:c085:11d::6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.28; Wed, 18 May 2022 16:37:21 -0700 Received: by devvm225.atn0.facebook.com (Postfix, from userid 425415) id A2522F3ED84F; Wed, 18 May 2022 16:37:12 -0700 (PDT) From: Stefan Roesch To: , , , , CC: , , Subject: [RFC PATCH v3 00/18] io-uring/xfs: support async buffered writes Date: Wed, 18 May 2022 16:36:51 -0700 Message-ID: <20220518233709.1937634-1-shr@fb.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-FB-Internal: Safe Content-Type: text/plain X-Proofpoint-ORIG-GUID: LkbB_RCgWkOzR0IA0Hu0aYF8OdjorBz_ X-Proofpoint-GUID: LkbB_RCgWkOzR0IA0Hu0aYF8OdjorBz_ X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.874,Hydra:6.0.486,FMLib:17.11.64.514 definitions=2022-05-18_06,2022-05-17_02,2022-02-23_01 Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org This patch series adds support for async buffered writes when using both xfs and io-uring. Currently io-uring only supports buffered writes in the slow path, by processing them in the io workers. With this patch series i= t is now possible to support buffered writes in the fast path. To be able to u= se the fast path the required pages must be in the page cache, the required = locks in xfs can be granted immediately and no additional blocks need to be rea= d form disk. Updating the inode can take time. An optimization has been implemented fo= r the time update. Time updates will be processed in the slow path. While t= here is already a time update in process, other write requests for the same fi= le, can skip the update of the modification time. =20 Performance results: For fio the following results have been obtained with a queue depth of 1 and 4k block size (runtime 600 secs): sequential writes: without patch with patch libaio psync iops: 77k 209k 195K 233K bw: 314MB/s 854MB/s 790MB/s 953M= B/s clat: 9600ns 120ns 540ns 3000n= s For an io depth of 1, the new patch improves throughput by over three tim= es (compared to the exiting behavior, where buffered writes are processed by= an io-worker process) and also the latency is considerably reduced. To achie= ve the same or better performance with the exisiting code an io depth of 4 is re= quired. Increasing the iodepth further does not lead to improvements. In addition the latency of buffered write operations is reduced considera= bly. Support for async buffered writes: To support async buffered writes the flag FMODE_BUF_WASYNC is introduce= d. In addition the check in generic_write_checks is modified to allow for asy= nc buffered writes that have this flag set. Changes to the iomap page create function to allow the caller to specif= y the gfp flags. Sets the IOMAP_NOWAIT flag in iomap if IOCB_NOWAIT has b= een set and specifies the requested gfp flags. Adds the iomap async buffered write support to the xfs iomap layer. Adds async buffered write support to the xfs iomap layer. Support for async buffered write support and inode time modification Splits the functions for checking if the file privileges need to be rem= oved in two functions: check function and a function for the removal of file pr= ivileges. The same split is also done for the function to update the file modific= ation time. Implement an optimization that while a file modification time is pendin= g other requests for the same file don't need to wait for the file modification= update.=20 This avoids that a considerable number of buffered async write requests= get punted. Take the ilock in nowait mode if async buffered writes are enabled and = enable the async buffered writes optimization in io_uring. Support for write throttling of async buffered writes: Add a no_wait parameter to the exisiting balance_dirty_pages() function= . The function will return -EAGAIN if the parameter is true and write throttl= ing is required. Add a new function called balance_dirty_pages_ratelimited_async() that = will be invoked from iomap_write_iter() if an async buffered write is requested= . =20 Enable async buffered write support in xfs This enables async buffered writes for xfs. Testing: This patch has been tested with xfstests and fio. Changes: V3: - Reformat new code in generic_write_checks_count() to line lengthof 80= . - Remove if condition in __iomap_write_begin to maintain current behavi= or. - use GFP_NOWAIT flag in __iomap_write_begin - rename need_file_remove_privs() function to file_needs_remove_privs() - rename do_file_remove_privs to __file_remove_privs() - add kernel documentation to file_remove_privs() function - rework else if branch in file_remove_privs() function - add kernel documentation to file_modified() function - add kernel documentation to file_modified_async() function - rename err variable in file_update_time to ret - rename function need_file_update_time() to file_needs_update_time() - rename function do_file_update_time() to __file_update_time() - don't move check for FMODE_NOCMTIME in generic helper - reformat __file_update_time for easier reading - add kernel documentation to file_update_time() function - fix if in file_update_time from < to <=3D - move modification of inode flags from do_file_update_time to file_mod= ified() When this function is called, the caller must hold the inode lock. - 3 new patches from Jan to add new no_wait flag to balance_dirty_pages= (), remove patch 12 from previous series - Make balance_dirty_pages_ratelimited_flags() a static function - Add new balance_dirty_pages_ratelimited_async() function =20 V2: - Remove atomic allocation - Use direct write in xfs_buffered_write_iomap_begin() - Use xfs_ilock_for_iomap() in xfs_buffered_write_iomap_begin() - Remove no_wait check at the end of xfs_buffered_write_iomap_begin() f= or the COW path. - Pass xfs_inode pointer to xfs_ilock_iocb and rename function to xfs_lock_xfs_inode - Replace existing uses of xfs_ilock_iocb with xfs_ilock_xfs_inode - Use xfs_ilock_xfs_inode in xfs_file_buffered_write() - Callers of xfs_ilock_for_iomap need to initialize lock mode. This is required so writes use an exclusive lock - Split of _balance_dirty_pages() from balance_dirty_pages() and return sleep time - Call _balance_dirty_pages() in balance_dirty_pages_ratelimited_flags(= ) - Move call to balance_dirty_pages_ratelimited_flags() in iomap_write_i= ter() to the beginning of the loop Jan Kara (3): mm: Move starting of background writeback into the main balancing loop mm: Move updates of dirty_exceeded into one place mm: Prepare balance_dirty_pages() for async buffered writes Stefan Roesch (15): block: Add check for async buffered writes to generic_write_checks iomap: Add iomap_page_create_gfp to allocate iomap_pages iomap: Use iomap_page_create_gfp() in __iomap_write_begin iomap: Add async buffered write support xfs: Add iomap async buffered write support fs: Split off remove_needs_file_privs() __remove_file_privs() fs: Split off file_needs_update_time and __file_update_time xfs: Enable async write file modification handling. fs: Optimization for concurrent file time updates. xfs: Add async buffered write support io_uring: Add support for async buffered writes mm: Add balance_dirty_pages_ratelimited_async() function iomap: Use balance_dirty_pages_ratelimited_flags in iomap_write_iter io_uring: Add tracepoint for short writes xfs: Enable async buffered write support fs/inode.c | 178 ++++++++++++++++++++++++-------- fs/io_uring.c | 32 +++++- fs/iomap/buffered-io.c | 71 +++++++++++-- fs/read_write.c | 4 +- fs/xfs/xfs_file.c | 36 +++---- fs/xfs/xfs_iomap.c | 14 ++- include/linux/fs.h | 7 ++ include/linux/writeback.h | 1 + include/trace/events/io_uring.h | 25 +++++ mm/page-writeback.c | 108 ++++++++++++------- 10 files changed, 352 insertions(+), 124 deletions(-) base-commit: 0cdd776ec92c0fec768c7079331804d3e52d4b27 --=20 2.30.2