[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200721193719.zx72xkbjvoake2po@alap3.anarazel.de>
Date: Tue, 21 Jul 2020 12:37:19 -0700
From: Andres Freund <andres@...razel.de>
To: Andy Lutomirski <luto@...nel.org>
Cc: Jens Axboe <axboe@...nel.dk>,
Stefano Garzarella <sgarzare@...hat.com>,
Christoph Hellwig <hch@....de>,
Kees Cook <keescook@...omium.org>,
Pavel Begunkov <asml.silence@...il.com>,
Miklos Szeredi <miklos@...redi.hu>,
Matthew Wilcox <willy@...radead.org>,
Jann Horn <jannh@...gle.com>,
Christian Brauner <christian.brauner@...ntu.com>,
strace-devel@...ts.strace.io, io-uring@...r.kernel.org,
Linux API <linux-api@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Michael Kerrisk <mtk.manpages@...il.com>,
Stefan Hajnoczi <stefanha@...hat.com>
Subject: Re: strace of io_uring events?
Hi,
On 2020-07-21 10:23:22 -0700, Andy Lutomirski wrote:
> Andres, how final is your Postgres branch?
Not final at all. Some of the constraints like needing to submit/receive
completions to/from multiple processes are pretty immovable though.
> I'm wondering if we could get away with requiring a special flag when
> creating an io_uring to indicate that you intend to submit IO from
> outside the creating mm.
Perhaps. It'd need to be clear when we need to do so, as we certainly
won't want to move the minimal kernel version further up.
But I think postgres is far from the only use case for wanting the
submitting mm to be the relevant one, not the creating one. It seems far
more dangerous to use the creating mm than the submitting mm. Makes
things like passing a uring fd with a few pre-opened files to another
process impossible.
Greetings,
Andres Freund
Powered by blists - more mailing lists