BPF List
 help / color / mirror / Atom feed
From: David Vernet <void@manifault.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: bpf@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
	Sean Christopherson <seanjc@google.com>,
	Vineeth Pillai <vineethrp@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Suleiman Souhlal <suleiman@google.com>
Subject: Re: [LSF/MM/BPF TOPIC] Implementing KVM vCPU Priority boosting via BPF
Date: Wed, 24 Jan 2024 11:15:32 -0600	[thread overview]
Message-ID: <20240124171532.GB253330@maniforge> (raw)
In-Reply-To: <653c2448-614e-48d6-af31-c5920d688f3e@joelfernandes.org>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Tue, Jan 23, 2024 at 09:59:50PM -0500, Joel Fernandes wrote:
> We should discuss a new approach for increasing KVM virtual CPU (vCPU) priority
> when guests need low latency. The last RFC posting [1] on this is thought to be
> too rigid and baking too much policy into the kernel. Incorporating complex
> policy logic directly into KVM seems problematic long-term for maintenance. Lets
> discuss leveraging BPF programs to offload more scheduling policy decisions to
> BPF / userspace.
> 
> Specific issues to discuss:
> 
> * Add support for enabling BPF programs to share memory and interface with guest.
> 
> * Create a kernel function allowing BPF programs to call sched_setscheduler(),
> facilitating priority boosting.
> 
> * UAPI concerns.
> 
> * Challenges with loading BPF programs in guest userspace we don't control.
> 
> [1] https://lore.kernel.org/all/20231214024727.3503870-1-vineeth@bitbyteword.org/

+1 to discussing all of the above at LSFMM, ideally as part of the BPF
track.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2024-01-24 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  2:59 [LSF/MM/BPF TOPIC] Implementing KVM vCPU Priority boosting via BPF Joel Fernandes
2024-01-24 17:15 ` David Vernet [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=20240124171532.GB253330@maniforge \
    --to=void@manifault.com \
    --cc=bpf@vger.kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rostedt@goodmis.org \
    --cc=seanjc@google.com \
    --cc=suleiman@google.com \
    --cc=vineethrp@gmail.com \
    /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