Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp835761ybh; Wed, 15 Jul 2020 17:13:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw8s0HOfyTgJmEqXZnQ2NAwXZRWkHXg0jQm4yLCgB7LdL1orvlxxppl230zdl7D308jHhn9 X-Received: by 2002:a17:906:c14f:: with SMTP id dp15mr1371994ejc.454.1594858381941; Wed, 15 Jul 2020 17:13:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594858381; cv=none; d=google.com; s=arc-20160816; b=WXf29UK2oh2u4gmWlHsoi5ZEPhOfZJK8GFb/12ow7UYfw9+LwKbh0zPMsYPqNYNS3x MtZYIefPJ3JagJARgaV3Y8Ibp75ZNoR2rbFW+g6uRfukMoRnHK8ae7mgjC7Ay+mux+fW GDkQenDifqe63EAosJTb8HR8f2GeMNMm8Hv13bgVSgoqkIXiF9pN1jJxzTid4e3rc0cY IAsU6h2opYK9IlznuohjOq54TvUxiayMU1kkzh6xLhFdAEypwsMq990JlMs3Fy+sKFhB fQdZ8r8hzp9GDvRDHqKIXGsw446VwrPsfTZYiwrpCZ19C2gleesQKmlT+mq+JXp6YeEh bolA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=enpcqnJaaGJhZIXTfiBWzOctgCsX8HJcte/tLqprN0E=; b=gulb/Jv548dBCTTirlyuKS5Kt1Ro2e46abnAJnK1dYOh+t1AOmj8gOGgvf3T/1jwOP JmJudBXpQ3SwWPYHoOt/UA0pTxty5kVzHX7nGE5vgdTO+ZGJkjAEYRFxdzRKRGrq1dKm Sb/+TGhW5Nk3IfPrIxOznHteP/W1cYWSzzMc37FeKGV5G+YvpXLEO+0TbA1AoHtRU1cj bpSoALp1Uwad7xmQzN0szIBlcnZCCZn3du3ICErLI3MDR5uADxRbzursNhiCux7+XzZj AeGy239vM2SrMTs0QsAk12NqxNtEc67J8N4XWZhnE/S4VizDTHe3ZWN5XgD/wlxcH7Lv yIYA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y5si623954edp.89.2020.07.15.17.12.37; Wed, 15 Jul 2020 17:13:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726965AbgGPAMe (ORCPT + 99 others); Wed, 15 Jul 2020 20:12:34 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:35417 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726479AbgGPAMe (ORCPT ); Wed, 15 Jul 2020 20:12:34 -0400 Received: from callcc.thunk.org (pool-96-230-252-158.bstnma.fios.verizon.net [96.230.252.158]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 06G0CCDh007246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 15 Jul 2020 20:12:13 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id 8BA07420304; Wed, 15 Jul 2020 20:12:12 -0400 (EDT) Date: Wed, 15 Jul 2020 20:12:12 -0400 From: tytso@mit.edu To: Matthew Wilcox Cc: Andy Lutomirski , Stefano Garzarella , Miklos Szeredi , Kees Cook , Christian Brauner , strace-devel@lists.strace.io, io-uring@vger.kernel.org, Pavel Begunkov , Linux API , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: strace of io_uring events? Message-ID: <20200716001212.GA388817@mit.edu> References: <20200715171130.GG12769@casper.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200715171130.GG12769@casper.infradead.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 15, 2020 at 06:11:30PM +0100, Matthew Wilcox wrote: > On Wed, Jul 15, 2020 at 07:35:50AM -0700, Andy Lutomirski wrote: > > > On Jul 15, 2020, at 4:12 AM, Miklos Szeredi wrote: > > > This thread is to discuss the possibility of stracing requests > > > submitted through io_uring. I'm not directly involved in io_uring > > > development, so I'm posting this out of interest in using strace on > > > processes utilizing io_uring. > > > > > > Is there some existing tracing infrastructure that strace could use to > > > get async completion events? Should we be introducing one? I suspect the best approach to use here is use eBPF, since since sending asyncronously to a ring buffer is going to be *way* more efficient than using the blocking ptrace(2) system call... - Ted