mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Vectored syscalls Was: [PATCH 0/3] readfile(2): a new syscall to make open/read/close faster
Date: Wed, 8 Jul 2020 17:45:36 +0200	[thread overview]
Message-ID: <48C35DFC-ED0A-4878-8AB7-1C4DC1BB6752@exactcode.com> (raw)
In-Reply-To: <20200708153859.GB715257@kroah.com>

Hey,

> On 8. Jul 2020, at 17:38, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> 
> 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.

Sure, but last time I check you can’t queue open, read, close like this ;-)

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


Well, given latest hardware security vulnerabilities it looks more useful
for real world applications than the very special case of just readfile(2) for
small to medium sized files, … any maybe more worth the effort of a new
system call.

	René

-- 
 ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com
 https://exactscan.com | https://ocrkit.com | https://t2sde.org | https://rene.rebe.de


      reply	other threads:[~2020-07-08 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 15:16 René Rebe
2020-07-08 15:38 ` Greg Kroah-Hartman
2020-07-08 15:45   ` René Rebe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48C35DFC-ED0A-4878-8AB7-1C4DC1BB6752@exactcode.com \
    --to=rene@exactcode.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®