public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: Demi Marie Obenour <demiobenour@gmail.com>
To: virtio-comment <virtio-comment@lists.linux.dev>
Subject: Asymptotic complexity of enabling and disabling MSI-X interrupts
Date: Mon, 6 Apr 2026 19:12:46 -0400	[thread overview]
Message-ID: <fdb110c6-0187-44b9-99f8-ffc3ecde5558@gmail.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 443 bytes --]

Is it okay for enabling and disabling an MSI-X interrupt vector to use
O(N) time, where N is the number of virtqueues assigned to that vector?
I am considering an implementation that uses one eventfd per virtqueue.
Each eventfd is registered with KVM as an irqfd.  Enabling or disabling
an MSI-X vector will require one ioctl for each virtqueue assigned
to that vector, which is O(N).
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2026-04-06 23:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=fdb110c6-0187-44b9-99f8-ffc3ecde5558@gmail.com \
    --to=demiobenour@gmail.com \
    --cc=virtio-comment@lists.linux.dev \
    /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