All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: lenb@kernel.org, hmh@hmh.eng.br, mingo@elte.hu,
	tglx@linutronix.de, tony.luck@gmail.com,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	gbeshers@sgi.com
Subject: Re: [RFC  - V2] - Mapping ACPI tables as CACHED
Date: Wed, 8 Dec 2010 21:50:25 -0600	[thread overview]
Message-ID: <20101209035025.GB6697@sgi.com> (raw)
In-Reply-To: <4D00308B.2040009@zytor.com>

On Wed, Dec 08, 2010 at 05:27:39PM -0800, H. Peter Anvin wrote:
> On 12/08/2010 01:22 PM, Jack Steiner wrote:
> > 
> > This patch substantially reduces the time to run ACPIDUMP on a large system:
> >  	527 seconds without the patch
> >  	  8 seconds with the patch
> > 
> 
> This is probably the worst possible motivation you can give here.
> Bootup time is much more of an issue.
> 
> However, this really needs Len's ack.

Sorry - should have included more info from the original posting.
The boot time speedup is the most critical. From the original mail:

	...
	The following experimental patch changes the kernel mapping for ACPI tables
	to CACHED. This eliminates the page attibute conflict & allows users to map
	the tables CACHEABLE. This significantly speeds up boot:

	        38 minutes without the patch
		27 minutes with the patch
		        ~30% improvement
	...

(Since the original posting, we've made additional reductions in
boot times. The absolute improvement from this patch is still the same
but the percentage improvement is now larger).


This is on a large SGI system. Boot time is reduced on smaller systems
but obviously the improvement is much less.

See the original mail for more details.

Len - the original patch had the cached/uncached mapping controlled by a
platform attribute (I'm paranoid). However, the community concensus was
that cached mappings were safe for all platforms.





--- jack

  reply	other threads:[~2010-12-09  3:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 15:22 [RFC] - Mapping ACPI tables as CACHED Jack Steiner
2010-07-22 15:52 ` Len Brown
2010-07-23 16:38   ` Jack Steiner
2010-07-23  1:46 ` ykzhao
2010-07-23  7:23   ` Ingo Molnar
2010-07-23 14:26     ` ykzhao
2010-08-17 14:45       ` Jack Steiner
2010-08-17 15:51       ` H. Peter Anvin
2010-08-17 14:42     ` Jack Steiner
2010-08-17 14:39   ` Jack Steiner
2010-07-24  0:14 ` Henrique de Moraes Holschuh
2010-07-24  0:45   ` Matthew Garrett
2010-07-24 12:26     ` Henrique de Moraes Holschuh
2010-08-17 14:49   ` Jack Steiner
2010-08-17 16:02     ` Linus Torvalds
2010-08-17 16:02       ` Linus Torvalds
2010-08-24 21:39   ` H. Peter Anvin
2010-08-26 17:17     ` [RFC - V2] " Jack Steiner
2010-08-26 18:08       ` H. Peter Anvin
2010-12-08 21:22         ` Jack Steiner
2010-12-09  1:27           ` H. Peter Anvin
2010-12-09  3:50             ` Jack Steiner [this message]
2010-12-09  6:12               ` Len Brown
2010-08-17 15:59 ` [RFC] " Jack Steiner
2010-08-26 17:47   ` Len Brown

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=20101209035025.GB6697@sgi.com \
    --to=steiner@sgi.com \
    --cc=gbeshers@sgi.com \
    --cc=hmh@hmh.eng.br \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@gmail.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 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.