linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Travis <travis@sgi.com>
Cc: mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
	msalter@redhat.com, dyoung@redhat.com, riel@redhat.com,
	peterz@infradead.org, mgorman@suse.de,
	linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] x86: Speed up ioremap operations
Date: Fri, 29 Aug 2014 13:16:02 -0700	[thread overview]
Message-ID: <20140829131602.72c422ebd2fd3fba426379e8@linux-foundation.org> (raw)
In-Reply-To: <20140829195328.511550688@asylum.americas.sgi.com>

On Fri, 29 Aug 2014 14:53:28 -0500 Mike Travis <travis@sgi.com> wrote:

> 
> We have a large university system in the UK that is experiencing
> very long delays modprobing the driver for a specific I/O device.
> The delay is from 8-10 minutes per device and there are 31 devices
> in the system.  This 4 to 5 hour delay in starting up those I/O
> devices is very much a burden on the customer.
> 
> There are two causes for requiring a restart/reload of the drivers.
> First is periodic preventive maintenance (PM) and the second is if
> any of the devices experience a fatal error.  Both of these trigger
> this excessively long delay in bringing the system back up to full
> capability.
> 
> The problem was tracked down to a very slow IOREMAP operation and
> the excessively long ioresource lookup to insure that the user is
> not attempting to ioremap RAM.  These patches provide a speed up
> to that function.
> 

Really would prefer to have some quantitative testing results in here,
as that is the entire point of the patchset.  And it leaves the reader
wondering "how much of this severe problem remains?".

Also, the -stable backport is a big ask, isn't it?  It's arguably
notabug and the affected number of machines is small.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2014-08-29 20:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 19:53 Mike Travis
2014-08-29 19:53 ` [PATCH 1/2] x86: Optimize resource lookups for ioremap Mike Travis
2014-08-29 19:53 ` [PATCH 2/2] x86: Use optimized ioresource lookup in ioremap function Mike Travis
2014-08-29 20:16 ` Andrew Morton [this message]
2014-08-29 20:44   ` [PATCH 0/2] x86: Speed up ioremap operations Mike Travis
2014-08-29 20:52     ` Andrew Morton
2014-08-29 22:31       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2014-08-29 19:16 Mike Travis
2014-08-27 22:59 Mike Travis
2014-08-27 23:06 ` Andrew Morton
2014-08-27 23:15   ` Mike Travis
2014-08-27 23:20     ` Andrew Morton
2014-08-27 23:30       ` Mike Travis
2014-08-28  6:48   ` Ingo Molnar

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=20140829131602.72c422ebd2fd3fba426379e8@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=msalter@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=travis@sgi.com \
    --cc=x86@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