All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] Re: [RFC] Some more io-thread optimizations
Date: Wed, 16 Feb 2011 09:26:06 +0100	[thread overview]
Message-ID: <4D5B8A1E.9000404@web.de> (raw)
In-Reply-To: <20110215220330.GA2547@amt.cnet>

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

On 2011-02-15 23:03, Marcelo Tosatti wrote:
> On Mon, Feb 14, 2011 at 10:50:42AM +0100, Jan Kiszka wrote:
>> Hi,
>>
>> patch below further reduces the io-thread overhead in tcg mode so that
>> specifically emulating smp boxes gets noticeably faster. Its essence:
>> poll the file descriptors until select returns 0, keeping the global
>> mutex locked. This reduces ping pong with the vcpu threads, most
>> noticeably in tcg mode where we run in lock-step.
>>
>> Split up in two patches, I'm planning to route those changes via the kvm
>> queue (as they collide with other patches there).
>>
>> Jan
> 
> Not sure this makes sense for all cases. There could be scenarios where
> a single pass is more efficient (think latency to acquire mutex from
> vcpu context in kvm mode, with intensive file IO in progress).

Yeah, likely true. Only TCG has these insane long lock-holding times and
requires signal-based mutex handover. I will exclude KVM from this.

Jan


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

      reply	other threads:[~2011-02-16  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14  9:50 [Qemu-devel] [RFC] Some more io-thread optimizations Jan Kiszka
2011-02-15 22:03 ` [Qemu-devel] " Marcelo Tosatti
2011-02-16  8:26   ` Jan Kiszka [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=4D5B8A1E.9000404@web.de \
    --to=jan.kiszka@web.de \
    --cc=aliguori@us.ibm.com \
    --cc=aurelien@aurel32.net \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.