public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Add clflush before monitor for Intel 7400 series
Date: Fri, 17 Oct 2008 13:13:15 -0700	[thread overview]
Message-ID: <48F8F1DB.9030202@zytor.com> (raw)
In-Reply-To: <7E82351C108FA840AB1866AC776AEC4637B798D6@orsmsx505.amr.corp.intel.com>

Pallipadi, Venkatesh wrote:
> 
> hpa,
> 
> Do you still have reservations about this being expensive.
> Note that this is only done when a CPU is about to go idle and
> The cost of clflush itself will be minimal compared to idle
> entry + idle exit latency.
> 

I guess I'm a bit confused about the tradeoff of CLFLUSH versus simply 
disabling MWAIT.  This is a relatively recent processor and so 
optimizing matters (if this was a P4 I would be more worried about what 
has least impact on the kernel as a whole.)

Entry and exit latency do matter (specifically, exit latency matters for 
longer waits and the combined entry+exit latency matters for short waits.)

On the other hand, perhaps what we need to do is to get the fix in and 
worry about performance later.

	-hpa

  reply	other threads:[~2008-10-17 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 21:00 [PATCH] x86: Add clflush before monitor for Intel 7400 series Venki Pallipadi
2008-10-07 21:09 ` H. Peter Anvin
2008-10-07 21:49   ` Venki Pallipadi
2008-10-07 23:02     ` H. Peter Anvin
2008-10-17 20:05       ` Pallipadi, Venkatesh
2008-10-17 20:13         ` H. Peter Anvin [this message]
2008-10-17 20:51           ` Pallipadi, Venkatesh
2008-10-17 22:49             ` H. Peter Anvin
2008-10-18  7:15               ` Andi Kleen

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=48F8F1DB.9030202@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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