From patchwork Sun Aug 9 06:30:36 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Zorro Lang X-Patchwork-Id: 11706547 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 8335D13B1 for ; Sun, 9 Aug 2020 06:30:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5EF0B2070B for ; Sun, 9 Aug 2020 06:30:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="N7oPktX6" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726097AbgHIGau (ORCPT ); Sun, 9 Aug 2020 02:30:50 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:25216 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726009AbgHIGau (ORCPT ); Sun, 9 Aug 2020 02:30:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1596954648; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=2qDBS5d6Q0gEY+bHXuulW7mVau/4p+SJT0xaNESHjYc=; b=N7oPktX6fVLx557g9O8ZxD2uzs/wLNoSotfBB6Da+MuGxnfnXITKCeoKU1BIVpg3/8R2Tq VFqnhlu9JrC360as6W1PJxwTi64UK0+e9WyJMh29kLOpLQokemIMm5Qd3B0aUWb3SzjC+L +oEgi9Z5YzoQ4CLtgMaY+7KChrhn3Bw= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-57-pbfF6HrCM_2ePmjdxPuwkQ-1; Sun, 09 Aug 2020 02:30:47 -0400 X-MC-Unique: pbfF6HrCM_2ePmjdxPuwkQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1CC0480183C; Sun, 9 Aug 2020 06:30:46 +0000 (UTC) Received: from localhost.localdomain.com (ovpn-12-33.pek2.redhat.com [10.72.12.33]) by smtp.corp.redhat.com (Postfix) with ESMTP id 886731C4; Sun, 9 Aug 2020 06:30:44 +0000 (UTC) From: Zorro Lang To: fstests@vger.kernel.org Cc: io-uring@vger.kernel.org, jmoyer@redhat.com Subject: [PATCH v2 0/4] fsstress,fsx: add io_uring test and do some fix Date: Sun, 9 Aug 2020 14:30:36 +0800 Message-Id: <20200809063040.15521-1-zlang@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Sender: fstests-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: fstests@vger.kernel.org This patchset tries to add new IO_URING test into fsstress [1/4] and fsx [4/4]. And then do some changes and bug fix by the way [2/4 and 3/4]. fsstress and fsx are important tools in xfstests to do filesystem I/Os test, lots of test cases use it. So add IO_URING operation into fsstress and fsx will help to cover IO_URING test from fs side. I'm not an IO_URING expert, so cc io-uring@ list, please feel free to tell me if you find something wrong or have any suggestions to improve the test. V2 did below changes: 1) 1/4 change the definition of URING_ENTRIES to 1 2) 2/4 change the difinition of AIO_ENTRIES to 1, undo an unrelated changed line 3) 4/4 turn to use io_uring_prep_readv/io_uring_prep_writev, due to old liburing(0.2-2) doesn't support io_uring_prep_read/io_uring_prep_write. Thanks, Zorro