public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "Brown, Len" <len.brown@intel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Stefan Lippers-Hollmann <s.L-H@gmx.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>
Subject: Re: patch acpi-remove-locking-from-pm1x_sts-register-reads.patch added to 2.6.28-stable tree
Date: Mon, 9 Feb 2009 09:12:54 -0800	[thread overview]
Message-ID: <20090209171254.GA24704@suse.de> (raw)
In-Reply-To: <E87738D94A6AD54789B5B8D1BAEB06CC49F143F02E@azsmsx503.amr.corp.intel.com>

On Mon, Feb 09, 2009 at 10:00:10AM -0700, Brown, Len wrote:
> 
> >> why is this -stable material?
> >> this is a performance improvement....
> >
> >It is, and not a bugfix?  If so, I'll drop it.
> 
> yes, removing the un-necessary locking
> it is a scaling performance improvement.
> 
> The code has been this way for years.
> The reason we noticed this issue recently
> is because of the emergence of systems that
> simultaneously have many threads and also
> have deep C-states.
> 
> In 2.6.30 we plan larger improvements in this area.

Ok, I'll go drop this patch from the -stable trees.

thanks,

greg k-h

  reply	other threads:[~2009-02-09 17:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090208211932.4CAB349019@coco.kroah.org>
2009-02-09  0:24 ` patch acpi-remove-locking-from-pm1x_sts-register-reads.patch added to 2.6.28-stable tree Stefan Lippers-Hollmann
2009-02-09 16:24   ` Greg KH
2009-02-09 16:30     ` Arjan van de Ven
2009-02-09 16:49       ` Greg KH
2009-02-09 17:00         ` Brown, Len
2009-02-09 17:12           ` Greg KH [this message]
2009-02-09 21:32     ` Stefan Lippers-Hollmann

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=20090209171254.GA24704@suse.de \
    --to=gregkh@suse.de \
    --cc=arjan@infradead.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.L-H@gmx.de \
    --cc=stable@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox