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=-0.5 required=3.0 tests=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 3AB1FC35246 for ; Sat, 1 Feb 2020 17:50:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 06B2720679 for ; Sat, 1 Feb 2020 17:50:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=anarazel.de header.i=@anarazel.de header.b="ZZ6iCw6f"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="SsvMrnPV" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726195AbgBARuC (ORCPT ); Sat, 1 Feb 2020 12:50:02 -0500 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]:52641 "EHLO wout5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726169AbgBARuC (ORCPT ); Sat, 1 Feb 2020 12:50:02 -0500 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id B19EB4DA; Sat, 1 Feb 2020 12:50:01 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sat, 01 Feb 2020 12:50:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:in-reply-to:references:mime-version:content-type :content-transfer-encoding:subject:to:from:message-id; s=fm3; bh=5TS5hi759PYWt+b/cjO+GMljg99HKUs0hvz9QQqZ4MI=; b=ZZ6iCw6fGIle HUIexnZhqHLVwMkKMpGfC7HRQMHmA5/tBhqWID5sb4CzJrmW6N0D+701MiNdOjNf zFkbvqoIgqlzCh/Zd+TSX4BadPKNPt7NvvVjSbit3Ga/Qe2vk8W3tLHLzFZohvpH L0jQ0dXnItpqDnVy/1WNUOT1OobpxkhC/Yv07xHThJ+RO2YOrIxHDIAEwAgrkR3V Fskx3tv1gtnq8YeOVwAAFTZ1iyoc4OG+zZ3MvOsND8uG4m6+WCNY3X/QHBR+GrdA eoHU0nD+KFe/bO1j680NmMPOdJ25wZ6ePTsZTXuRL8WglO31cJglUExxgQqzs9dr aktmMREs9g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=5TS5hi759PYWt+b/cjO+GMljg99HKUs0hvz9QQqZ4 MI=; b=SsvMrnPVRjFsA+77e9NtfUoWpssXVKfBEQdfWflO6tnGwaIDP8FDz41wp mYpq7cWUZU532qT19xTZjQlbutrDUNWQ/1BmSTo/v9JXXHVEE1o0acKMzJcHIdFh lNuZhX3BRXYAr45i+AjnsnYRWcQDc6BN2Dj+myuu02sVjYERXz1aLdwhtnJFG1iv MLMhWG0H6Eb1sChgkop+EqD87IQJnqfOqHy0E+F/G9x2isAzHyoZK8UNrRl4JuWe h1mrZU3ws3ZNMGhrsEyOY71JIQYopszSxc3OlZAKJu8XhpYHZcLIeMGky+bSaHs/ O9+7yS6Gr1h/GCt+Y9gugP6FVJZJA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrgedvgddutdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepffgfjghfgggtgffuvffhkfesthhqmhdttderjeenucfhrhhomheptehnughr vghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecukfhppe dujedvrdehkedruddtjedrudekieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrnhgurhgvshesrghnrghrrgiivghlrdguvg X-ME-Proxy: Received: from [100.170.113.13] (unknown [172.58.107.186]) by mail.messagingengine.com (Postfix) with ESMTPA id 78415328005A; Sat, 1 Feb 2020 12:50:00 -0500 (EST) Date: Sat, 01 Feb 2020 18:49:53 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: <20200201125350.vkkhezidm6ka6ux5@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: liburing: expose syscalls? To: Jens Axboe , io-uring@vger.kernel.org From: Andres Freund Message-ID: <78A9EC3E-0961-4EF3-A226-1FCA34FAF818@anarazel.de> Sender: io-uring-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org Hi,=20 On February 1, 2020 6:39:41 PM GMT+01:00, Jens Axboe w= rote: >On 2/1/20 5:53 AM, Andres Freund wrote: >> Hi, >>=20 >> As long as the syscalls aren't exposed by glibc it'd be useful - at >> least for me - to have liburing expose the syscalls without really >going >> through liburing facilities=2E=2E=2E >>=20 >> Right now I'm e=2Eg=2E using a "raw" >io_uring_enter(IORING_ENTER_GETEVENTS) >> to be able to have multiple processes safely wait for events on the >same >> uring, without needing to hold the lock [1] protecting the ring [2]=2E= =20 >It's >> probably a good idea to add a liburing function to be able to do so, >but >> I'd guess there are going to continue to be cases like that=2E In a bit >> of time it seems likely that at least open source users of uring that >> are included in databases, have to work against multiple versions of >> liburing (as usually embedding libs is not allowed), and sometimes >that >> is easier if one can backfill a function or two if necessary=2E >>=20 >> That syscall should probably be under a name that won't conflict with >> eventual glibc implementation of the syscall=2E >>=20 >> Obviously I can just do the syscall() etc myself, but it seems >> unnecessary to have a separate copy of the ifdefs for syscall numbers >> etc=2E >>=20 >> What do you think? > >Not sure what I'm missing here, but liburing already has >__sys_io_uring_enter() for this purpose, and ditto for the register >and setup functions? Aren't they hidden to the outside by the symbol versioning script? Andres --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E