From: Sean Christopherson <seanjc@google.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
pbonzini@redhat.com, John Levon <john.levon@nutanix.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Thanos Makatos <thanos.makatos@nutanix.com>
Subject: Re: [PATCH] KVM: optionally post write on ioeventfd write
Date: Sun, 4 Oct 2026 22:11:50 -0700 [thread overview]
Message-ID: <asMxlgG0BzCJvgDm@google.com> (raw)
In-Reply-To: <c18ef5464ff4fb4d607c6ae02c58024b41b3f17c.camel@infradead.org>
On Sun, Oct 04, 2026, David Woodhouse wrote:
> FWIW while this is sufficient for implementing i82599 VF emulation, to
> get line-rate TCP *performance* I also needed a directed yield_to() to
> the consumer worker thread when it gets triggered.
>
> And to get line-rate *UDP* performance I needed the consumer to be able
> to arm/disarm it, to avoid getting throttled into lockstep with the
> guest.
By "it", do you mean (a) the eventfd, (b) the yield_to() behavior, (c) both, or
(d) something else entirely?
> I'll clean up my proof of concept hacks and post them after LPC.
next prev parent reply other threads:[~2026-10-05 5:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 12:56 [PATCH] KVM: optionally post write on ioeventfd write Thanos Makatos
2026-03-12 15:02 ` David Woodhouse
2026-03-12 16:12 ` Thanos Makatos
2026-04-21 14:44 ` Sean Christopherson
2026-09-19 15:59 ` David Woodhouse
2026-03-23 15:01 ` Thanos Makatos
2026-04-10 19:11 ` Thanos Makatos
2026-04-21 14:45 ` Sean Christopherson
2026-06-10 7:31 ` John Levon
2026-09-22 13:51 ` Stefan Hajnoczi
2026-09-22 15:28 ` David Woodhouse
2026-09-22 16:47 ` Sean Christopherson
2026-10-04 16:16 ` David Woodhouse
2026-10-05 5:11 ` Sean Christopherson [this message]
2026-09-22 17:03 ` Sean Christopherson
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 20:00 [RFC PATCH] KVM: optionally commit " Sean Christopherson
2026-03-02 12:28 ` [PATCH] KVM: optionally post " Thanos Makatos
2026-03-05 1:26 ` Sean Christopherson
2026-03-06 11:14 ` Thanos Makatos
2026-03-05 1:49 ` kernel test robot
2026-03-05 9:39 ` kernel test robot
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=asMxlgG0BzCJvgDm@google.com \
--to=seanjc@google.com \
--cc=dwmw2@infradead.org \
--cc=john.levon@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=thanos.makatos@nutanix.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