From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [10.7.7.5] (unknown [182.253.183.240]) by gnuweeb.org (Postfix) with ESMTPSA id 3372C8166D; Thu, 24 Nov 2022 11:47:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1669290450; bh=eiWoW7SsKexMoYK+aXHgvZrDbaN0ONDDt4rC72Y21aQ=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=UmWUU/sZ4uj9unRYIZMI8CWaYypc3mNhPN4ExuAeBLf4QbXgtGL5iND/PbfNYdgE5 GVHvV4btUDODFo1BOKgWJzMIpK890X4UZur01NiZW31SKmHU/QHchi7lN6A2jCcSkI dnj1j/J7bU1S/bHXBBrMBAHxJegJ1X2NNW1NTkT25OQxWNPMQ6X40B38lyX3f+fNUx YlxQ3ophoFYiNpZopkbCMnfENp6kAJEY+UNg8M+2rr8mu+R1t9PTJppf/8DaVKVXWD 4ODdgQFGBnHrtMMRqV8PsRevh8MflgFP2AukZTGVzi4/t150wDtaeFsrj280HvH57e bIj4313FBrDJw== Message-ID: Date: Thu, 24 Nov 2022 18:47:24 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Content-Language: en-US To: Dylan Yudaken Cc: Jens Axboe , Pavel Begunkov , Gilang Fachrezy , Alviro Iskandar Setiawan , Muhammad Rizki , io-uring Mailing List , GNU/Weeb Mailing List , VNLX Kernel Department References: <20221124075846.3784701-1-ammar.faizi@intel.com> <20221124075846.3784701-2-ammar.faizi@intel.com> From: Ammar Faizi Subject: Re: [PATCH liburing v1 1/7] liburing.h: Export `__io_uring_flush_sq()` function In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 11/24/22 5:14 PM, Dylan Yudaken wrote: > I think changing the tests to use the public API is probably better > than exporting this function. I don't believe it has much general use? But there is no public API that does the same thing. I'll mark it as static and create a copy of that function in iopoll.c (in v2). Something like this, what do you think? src/queue.c | 2 +- test/iopoll.c | 33 ++++++++++++++++++++++++++++++++- 2 files changed, 33 insertions(+), 2 deletions(-) diff --git a/src/queue.c b/src/queue.c index feea0ad..b784b10 100644 --- a/src/queue.c +++ b/src/queue.c @@ -201,7 +201,7 @@ again: * Sync internal state with kernel ring state on the SQ side. Returns the * number of pending items in the SQ ring, for the shared ring. */ -unsigned __io_uring_flush_sq(struct io_uring *ring) +static unsigned __io_uring_flush_sq(struct io_uring *ring) { struct io_uring_sq *sq = &ring->sq; unsigned tail = sq->sqe_tail; diff --git a/test/iopoll.c b/test/iopoll.c index 20f91c7..5edd5c3 100644 --- a/test/iopoll.c +++ b/test/iopoll.c @@ -201,7 +201,38 @@ err: return 1; } -extern unsigned __io_uring_flush_sq(struct io_uring *ring); +/* + * Sync internal state with kernel ring state on the SQ side. Returns the + * number of pending items in the SQ ring, for the shared ring. + */ +static unsigned __io_uring_flush_sq(struct io_uring *ring) +{ + struct io_uring_sq *sq = &ring->sq; + unsigned tail = sq->sqe_tail; + + if (sq->sqe_head != tail) { + sq->sqe_head = tail; + /* + * Ensure kernel sees the SQE updates before the tail update. + */ + if (!(ring->flags & IORING_SETUP_SQPOLL)) + IO_URING_WRITE_ONCE(*sq->ktail, tail); + else + io_uring_smp_store_release(sq->ktail, tail); + } + /* + * This _may_ look problematic, as we're not supposed to be reading + * SQ->head without acquire semantics. When we're in SQPOLL mode, the + * kernel submitter could be updating this right now. For non-SQPOLL, + * task itself does it, and there's no potential race. But even for + * SQPOLL, the load is going to be potentially out-of-date the very + * instant it's done, regardless or whether or not it's done + * atomically. Worst case, we're going to be over-estimating what + * we can submit. The point is, we need to be able to deal with this + * situation regardless of any perceived atomicity. + */ + return tail - *sq->khead; +} /* * if we are polling io_uring_submit needs to always enter the -- Ammar Faizi