Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 10 Jul 2020 11:33:09 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: Jens Axboe <axboe@...nel.dk>, Sargun Dhillon <sargun@...gun.me>,
        Kees Cook <keescook@...omium.org>, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Kernel Hardening <kernel-hardening@...ts.openwall.com>,
        Jann Horn <jannh@...gle.com>, Aleksa Sarai <asarai@...e.de>,
        Christian Brauner <christian.brauner@...ntu.com>,
        Stefan Hajnoczi <stefanha@...hat.com>, io-uring@...r.kernel.org,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Jeff Moyer <jmoyer@...hat.com>
Subject: Re: [PATCH RFC 0/3] io_uring: add restrictions to support untrusted
 applications and guests

.snip..
> Just to recap the proposal, the idea is to add some restrictions to the
> operations (sqe, register, fixed file) to safely allow untrusted applications
> or guests to use io_uring queues.

Hi!

This is neat and quite cool - but one thing that keeps nagging me is
what how much overhead does this cut from the existing setup when you use
virtio (with guests obviously)? That is from a high level view the
beaty of io_uring being passed in the guest is you don't have the
virtio ring -> io_uring processing, right?

Thanks!

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.