From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-178.mta1.migadu.com (out-178.mta1.migadu.com [95.215.58.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EB9E420DD2 for ; Thu, 30 May 2024 16:10:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.178 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717085413; cv=none; b=h9Nw/HdgpiXlOVmZ6AZYSonkXoeX7XT+84/0OhoR2rWFGpFO0J0vuL9DA6f5poL1k0lGQQ4fGYwKmbzSI3BsN2Ce0HhZrOPos6CGqPJAhNt5r/Mjn8w4q5IJ/sotl4Bbrc66J/IdSW9wlGTJLNwjJwpzyfsLHK6FNbZCEK/xISY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717085413; c=relaxed/simple; bh=eky9KFR1Nfbhxq2hpON/XxipQzCyHD4DlpmijR76MDw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=e2eWTkMyyAGGtW8ql4mYkKluigq/0h+knzcWVYR1jnuhT8uqshw7iJajpAzErQm6zYN4jSJS1WJVKJ6QTdmqU4Yvj1C9pKI5+OW7x92RJXy1l1gLet4aQUzNp/ZXti8q3SAMRU7a/UaOLIcCx6n0JpF5eS27tBymCJnXXix2P3o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=ZDqoIibk; arc=none smtp.client-ip=95.215.58.178 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="ZDqoIibk" X-Envelope-To: bernd.schubert@fastmail.fm DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1717085406; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wiTcEP6Pa5LKEim0NuYDG7k+chuGfMv3rkOy5FDKhZA=; b=ZDqoIibkVoem+zw2/+b7DjzDNmz86Nc1mXnpxY0UeCByeQ3sCqsAOWadn1A4EVP8S3jIUk vuPvMBysx/Ztlw0nj5XlH7zUzkJo6S7DDfbk6YMlZS2bCbaecAec7HWpdAiMpOQGeSleOA TpY9tOkou+qrYwabw+7lZbbzJrBHMbw= X-Envelope-To: bschubert@ddn.com X-Envelope-To: miklos@szeredi.hu X-Envelope-To: amir73il@gmail.com X-Envelope-To: linux-fsdevel@vger.kernel.org X-Envelope-To: akpm@linux-foundation.org X-Envelope-To: linux-mm@kvack.org X-Envelope-To: mingo@redhat.com X-Envelope-To: peterz@infradead.org X-Envelope-To: avagin@google.com X-Envelope-To: io-uring@vger.kernel.org X-Envelope-To: axboe@kernel.dk X-Envelope-To: ming.lei@redhat.com X-Envelope-To: asml.silence@gmail.com X-Envelope-To: josef@toxicpanda.com Date: Thu, 30 May 2024 12:10:00 -0400 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Kent Overstreet To: Bernd Schubert Cc: Bernd Schubert , Miklos Szeredi , Amir Goldstein , linux-fsdevel@vger.kernel.org, Andrew Morton , linux-mm@kvack.org, Ingo Molnar , Peter Zijlstra , Andrei Vagin , io-uring@vger.kernel.org, Jens Axboe , Ming Lei , Pavel Begunkov , Josef Bacik Subject: Re: [PATCH RFC v2 00/19] fuse: fuse-over-io-uring Message-ID: References: <20240529-fuse-uring-for-6-9-rfc2-out-v1-0-d149476b1d65@ddn.com> <5mimjjxul2sc2g7x6pttnit46pbw3astwj2giqfr4xayp63el2@fb5bgtiavwgv> <8c3548a9-3b15-49c4-9e38-68d81433144a@fastmail.fm> Precedence: bulk X-Mailing-List: io-uring@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8c3548a9-3b15-49c4-9e38-68d81433144a@fastmail.fm> X-Migadu-Flow: FLOW_OUT On Thu, May 30, 2024 at 06:02:21PM +0200, Bernd Schubert wrote: > Hmm, initially I had thought about writing my own ring buffer, but then > io-uring got IORING_OP_URING_CMD, which seems to have exactly what we > need? From interface point of view, io-uring seems easy to use here, > has everything we need and kind of the same thing is used for ublk - > what speaks against io-uring? And what other suggestion do you have? > > I guess the same concern would also apply to ublk_drv. > > Well, decoupling from io-uring might help to get for zero-copy, as there > doesn't seem to be an agreement with Mings approaches (sorry I'm only > silently following for now). > > From our side, a customer has pointed out security concerns for io-uring. > My thinking so far was to implemented the required io-uring pieces into > an module and access it with ioctls... Which would also allow to > backport it to RHEL8/RHEL9. Well, I've been starting to sketch out a ringbuffer() syscall, which would work on any (supported) file descriptor and give you a ringbuffer for reading or writing (or call it twice for both). That seems to be what fuse really wants, no? You're already using a file descriptor and your own RPC format, you just want a faster communications channel.