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=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 8F04CC4707A for ; Sun, 23 May 2021 16:20:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 61FD260C3F for ; Sun, 23 May 2021 16:20:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231835AbhEWQVt (ORCPT ); Sun, 23 May 2021 12:21:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48830 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231818AbhEWQVs (ORCPT ); Sun, 23 May 2021 12:21:48 -0400 Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C94B5C061574 for ; Sun, 23 May 2021 09:20:19 -0700 (PDT) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpwn.com; s=key1; t=1621786816; 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=EnzDhDn76D2l7zwUFMcgAQTB5GhGZnfvqm1QXn6n14k=; b=k6b9N+bzLgsMPuwVqx37GuYNbsdEYVb993jiOV/329MjnmkSmJjjI9sEJJ8qEvh7AzI2Mv xEPRENm5yStZhcCRlsHtP4uh5D5dJ3Cek1K9S7IhTZ54zVHRZKUnuAzg43HvCOBY8TmUdQ sK/LbenT3Sgf8FFLRVc8e/uuxeUE2LmP/0jUa7l3tolegTtMZALlGC6jo0MmAbgfwNeOhb Xj07fB/uOub5C5WTRzfWk0I88iWDvOar68K4h8CyVD4XQlNqUWYkaoezQB0qXS0Ln/5dzw fK+xX8hi3epmfCOiG25gZHN3xlh3UpfS2YZ+tunnZCaCi8tanNKRLIfhvN6ZXQ== From: Drew DeVault To: io-uring@vger.kernel.org Cc: Drew DeVault , Jens Axboe , Pavel Begunkov Subject: [PATCH] io_uring_enter(2): clarify OP_READ and OP_WRITE Date: Sun, 23 May 2021 12:20:12 -0400 Message-Id: <20210523162012.10052-1-sir@cmpwn.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: sir@cmpwn.com Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org These do not advance the internal file offset, making them behave more like pread/pwrite than read/write. --- man/io_uring_enter.2 | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2 index f898ffd..81044c1 100644 --- a/man/io_uring_enter.2 +++ b/man/io_uring_enter.2 @@ -576,16 +576,18 @@ for the general description of the related system call. Available since 5.6. .TP .B IORING_OP_WRITE Issue the equivalent of a -.BR read(2) +.BR pread(2) or -.BR write(2) +.BR pwrite(2) system call. .I fd is the file descriptor to be operated on, .I addr -contains the buffer in question, and +contains the buffer in question, .I len -contains the length of the IO operation. These are non-vectored versions of the +contains the length of the IO operation, and +.I offs +contains the read or write offset. These are non-vectored versions of the .B IORING_OP_READV and .B IORING_OP_WRITEV -- 2.31.1