public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Spencer Baugh <[email protected]>, [email protected]
Subject: Re: FlexSC influence on io_uring
Date: Mon, 31 Jan 2022 12:22:22 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 1/31/22 11:55 AM, Spencer Baugh wrote:
> 
> Hi,
> 
> To what extent, if any, was the FlexSC paper an influence on io_uring?
> 
> FlexSC is described in a paper from 2010:
> https://www.usenix.org/legacy/events/osdi10/tech/full_papers/Soares.pdf
> 
> FlexSC is a system for asynchronous system calls aimed at achieving
> high-performance by avoiding the cost of system calls, in particular the
> locality costs of executing kernel code and user code on the same core.
> 
> Implementation-wise, it seems broadly similar to io_uring, in that
> system calls are submitted by writing to some location in memory, which
> is later picked up by a syscall-execution thread (ala
> IORING_SETUP_SQPOLL) which executes it and writes back the result.
> 
> I'm just curious if there was any influence from FlexSC on io_uring.

Wasn't aware of this paper, if that answers the question. The idea for
async syscalls (to me) date back to the original threadlet/acall ideas
from Zach Brown and Ingo, though my implementation ended up being vastly
different. The API with the rings of shared memory was a pretty obvious
one and not really novel, it's been used in both sw and hw for a long
time.

-- 
Jens Axboe


      reply	other threads:[~2022-01-31 19:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 18:55 FlexSC influence on io_uring Spencer Baugh
2022-01-31 19:22 ` Jens Axboe [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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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