All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Frediano Ziglio <freddy77@gmail.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] posix-aio-compat: fix latency issues
Date: Mon, 08 Aug 2011 16:26:25 +0300	[thread overview]
Message-ID: <4E3FE401.6080701@redhat.com> (raw)
In-Reply-To: <CAHt6W4eyfPHKNUzmPkmKd+xEMobEJXaM7jKZDJMLD-4UOpnNfA@mail.gmail.com>

On 08/08/2011 04:21 PM, Frediano Ziglio wrote:
> >
> >  The entire qemu process may be affined to a subset of the host cpus; we
> >  don't want to break that.
> >
> >  For example:
> >
> >     taskset 0xf0 qemu ....
> >     (qemu) info cpus
> >  <pin individual vcpu threads to host cpus>
> >
> >
>
> Just call sched_getaffinity at program start, save to a global
> variable and then set this affinity for io threads.

This affinity may change later on.

> I didn't use affinity that much but from manual it seems that if you
> own process you can set affinity as you like.
> IMHO this patch introduce a delay in io thread creation due to posting
> thread creation to another thread just to set different affinity.

It does.  But aio threads have a long life, so this happens very rarely.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-08-08 13:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 11:37 [PATCH] posix-aio-compat: fix latency issues Avi Kivity
2011-08-08 11:37 ` [Qemu-devel] " Avi Kivity
2011-08-08 12:34 ` Anthony Liguori
2011-08-08 12:34   ` [Qemu-devel] " Anthony Liguori
2011-08-08 12:42   ` Avi Kivity
2011-08-08 12:49 ` Frediano Ziglio
2011-08-08 12:54   ` Avi Kivity
2011-08-08 12:54     ` [Qemu-devel] " Avi Kivity
2011-08-08 13:21     ` Frediano Ziglio
2011-08-08 13:26       ` Avi Kivity [this message]
2011-08-12 13:24 ` Anthony Liguori
2011-08-12 13:24   ` Anthony Liguori
2011-08-14  3:43   ` Avi Kivity
2011-08-14  3:43     ` [Qemu-devel] " Avi Kivity

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=4E3FE401.6080701@redhat.com \
    --to=avi@redhat.com \
    --cc=freddy77@gmail.com \
    --cc=kvm@vger.kernel.org \
    --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.