linux-kernel - Re: Vectored syscalls Was: [PATCH 0/3] readfile(2): a new syscall to make open/read/close faster

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 8 Jul 2020 17:38:59 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     René Rebe <rene@...ctcode.com>
Cc:     linux-kernel@...r.kernel.org, viro@...iv.linux.org
Subject: Re: Vectored syscalls Was: [PATCH 0/3] readfile(2): a new syscall to
 make open/read/close faster

On Wed, Jul 08, 2020 at 05:16:41PM +0200, René Rebe wrote:
> Hey there,
> 
> maybe instead of this rather specific, niche readfile syscall, would it not be beneficial
> to allow issuing any group or bundle of several arbitrary system calls so this could also
> be used to speed up other, more demanding high performance applications that need
> a bit more than just readfile()?

Why not just use io_uring for that for I/O calls, that's what it is
designed for.

More "generic" syscall batching always ends up falling down in
complexity anytime anyone tries it.  Good luck!

greg k-h