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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CD366C433FE for ; Tue, 14 Jul 2020 08:07:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AC40421582 for ; Tue, 14 Jul 2020 08:07:16 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=szeredi.hu header.i=@szeredi.hu header.b="El1qSrVl" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725793AbgGNIHQ (ORCPT ); Tue, 14 Jul 2020 04:07:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51304 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725816AbgGNIHP (ORCPT ); Tue, 14 Jul 2020 04:07:15 -0400 Received: from mail-ed1-x544.google.com (mail-ed1-x544.google.com [IPv6:2a00:1450:4864:20::544]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DAC33C061794 for ; Tue, 14 Jul 2020 01:07:14 -0700 (PDT) Received: by mail-ed1-x544.google.com with SMTP id e22so16158889edq.8 for ; Tue, 14 Jul 2020 01:07:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VxG136uE7k/7DQKw2dWH82lAeA2t/fDkcPS0g4RMW9A=; b=El1qSrVlx5j8OzqWY+jAkGIyxjaAfYH+cAXX/jS9K9Nm7LDsD7Ow20X6ZI/9L4i34m i6WsR0CtSO9QTmeXYDIWsjH1tlcEOcfyjR+Yn6OuRbJMAlEjvHkjEtfJJvDtJKZFb57q UXgWM5FxsZRScs6IL4dz92fo4cR62DnQk6wXY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VxG136uE7k/7DQKw2dWH82lAeA2t/fDkcPS0g4RMW9A=; b=BDFH8t3AVNnuX1mS1H2er9p2R2tDyl5uitj2GX3z6WzCl1rHE5PRUg8gwwaz/LWPj0 Mei83OP53ovGLUbWr2rRKA44fIl9Av9IU0x96y63xYbrlerw6ZVwe9mAVi7ItDWblC2R aGcMBYvMXhwKH1BwTtzkJKCL7f41Nc1rkBdbKLEITyLoD7g5zHOFAqk/d8NxJZPmhNBk e6ht6+zR72G0W5Leu4oSbn4jOr+N6qD36NmP0Ua7D/PBkYVbierMQa9spTWTDI8L3Br+ ZHnqFXz3H3Z31kq+C7x54VkJzGm0udsrwhUIQxwyjFgx20aI93S72IvYV3jDzFiSk4fT gOeQ== X-Gm-Message-State: AOAM5329dTkla0Lky0BSdTQJgNi/Ezf1GA/LI5hCDUhJDtp7NcOE6kRt zzLW4fLWtu25DFLbagPhwp4XOnauvlyYI8C6JWSuiw== X-Google-Smtp-Source: ABdhPJzWasYoseKAcvHkcWBtEYPiZDeYidABizN8Y9lJDS4GoTapol5Yea6vIlDc4ozwIskC2c/AS3sLTWFc+1jaNwk= X-Received: by 2002:a05:6402:1687:: with SMTP id a7mr3263957edv.358.1594714033497; Tue, 14 Jul 2020 01:07:13 -0700 (PDT) MIME-Version: 1.0 References: <20200705115021.GA1227929@kroah.com> <20200714065110.GA8047@amd> In-Reply-To: <20200714065110.GA8047@amd> From: Miklos Szeredi Date: Tue, 14 Jul 2020 10:07:02 +0200 Message-ID: Subject: Re: [PATCH 0/3] readfile(2): a new syscall to make open/read/close faster To: Pavel Machek Cc: Greg KH , Jan Ziak <0xe2.0x9a.0x9b@gmail.com>, Linux API , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-man , Michael Kerrisk , shuah@kernel.org, Al Viro , io-uring@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: io-uring-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On Tue, Jul 14, 2020 at 8:51 AM Pavel Machek wrote: > > Hi! > > > > At first, I thought that the proposed system call is capable of > > > reading *multiple* small files using a single system call - which > > > would help increase HDD/SSD queue utilization and increase IOPS (I/O > > > operations per second) - but that isn't the case and the proposed > > > system call can read just a single file. > > > > If you want to do this for multple files, use io_ring, that's what it > > was designed for. I think Jens was going to be adding support for the > > open/read/close pattern to it as well, after some other more pressing > > features/fixes were finished. > > What about... just using io_uring for single file, too? I'm pretty > sure it can be wrapped in a library that is simple to use, avoiding > need for new syscall. Just wondering: is there a plan to add strace support to io_uring? And I don't just mean the syscalls associated with io_uring, but tracing the ring itself. I think that's quite important as io_uring becomes mainstream. Thanks, Miklos