ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: ksummit@lists.linux.dev
Subject: Re: [TECH TOPIC] io_uring: BPF controlled I/O
Date: Fri, 25 Jun 2021 19:28:14 +0100	[thread overview]
Message-ID: <66afa1cd-aeb9-1103-87b5-ab27734871d4@gmail.com> (raw)
In-Reply-To: <b13d6f81-1679-dada-5bdf-1f94e0ba44c1@gmail.com>

On 6/25/21 7:24 PM, Pavel Begunkov wrote:

Please ignore this:

My apologies, looks I screwed it and misread instructions.
ignore this submission.

> io_uring is an asynchronous I/O API crafted for efficiency, where one of
> the reasons for using shared rings is to reduce context switching. It got
> lots of of features since introduction, and pushing it further we want
> to give away some of the control over submitting and controlling I/O to
> BPF, minimising the number of context switches even more.
> - It should keep the number of system calls to a minimum.
> - Help to lower overhead on scheduling user processes to CPUs
>   when they have not much to do and will go to sleep briefly.
> - Be an alternative to submission queue polling for latency
>   reduction not taking as much CPU time at the same moment.
> We'll go over the current design [1] and decisions, issues and plans,
> and hopefully it will engage a discussion and give impetus to curious
> minds to try it out and share ideas on how to tailor the API to fit
> their use cases.
> [1] https://lore.kernel.org/io-uring/a83f147b-ea9d-e693-a2e9-c6ce16659749@gmail.com/T/#m31d0a2ac6e2213f912a200f5e8d88bd74f81406b

Pavel Begunkov

      reply	other threads:[~2021-06-25 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 18:24 Pavel Begunkov
2021-06-25 18:28 ` Pavel Begunkov [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:

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

  git send-email \
    --in-reply-to=66afa1cd-aeb9-1103-87b5-ab27734871d4@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=ksummit@lists.linux.dev \
    --subject='Re: [TECH TOPIC] io_uring: BPF controlled I/O' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).