From: Arjan van de Ven <arjan@infradead.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>, Jens Axboe <jens.axboe@oracle.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH RFC 3/3] x86: use mwait for trigger API
Date: Sat, 16 Aug 2008 15:31:09 -0700 [thread overview]
Message-ID: <20080816153109.3469878c@infradead.org> (raw)
In-Reply-To: <48A74BAA.4010908@goop.org>
On Sat, 16 Aug 2008 14:50:34 -0700
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Arjan van de Ven wrote:
> > monitor/mwait is rather really expensive.. are we really sure we
> > want to use this?
> > (from an Intel cpu perspective the answer is very likely no; but I
> > don't know what AMD does here)
> >
>
> The intended use is when you're going to be waiting for a while (on
> the order of microseconds or more).
well mwait really is not cheap, I'd not be surprised if it's in that
same order.
> In the Xen case, I use this to
> block the vcpu if we pass a few iterations without the condition
> being true. While the mwait patch doesn't do this at present, it
> could.
that's another hard one.. passing C-state hints into mwait needs ACPI
help; the BIOS tells us which mwait values are legal/valid at any point
in time.. but this gets tricky to put into these spinpletions.
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-08-16 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 16:34 [PATCH RFC 3/3] x86: use mwait for trigger API Jeremy Fitzhardinge
2008-08-16 17:44 ` Arjan van de Ven
2008-08-16 21:50 ` Jeremy Fitzhardinge
2008-08-16 22:31 ` Arjan van de Ven [this message]
2008-08-28 12:25 ` Christian Borntraeger
2008-08-28 17:33 ` Jeremy Fitzhardinge
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=20080816153109.3469878c@infradead.org \
--to=arjan@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=borntraeger@de.ibm.com \
--cc=jens.axboe@oracle.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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.