[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140829131602.72c422ebd2fd3fba426379e8@linux-foundation.org>
Date: Fri, 29 Aug 2014 13:16:02 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mike Travis <travis@....com>
Cc: mingo@...hat.com, tglx@...utronix.de, hpa@...or.com,
msalter@...hat.com, dyoung@...hat.com, riel@...hat.com,
peterz@...radead.org, mgorman@...e.de,
linux-kernel@...r.kernel.org, x86@...nel.org, linux-mm@...ck.org
Subject: Re: [PATCH 0/2] x86: Speed up ioremap operations
On Fri, 29 Aug 2014 14:53:28 -0500 Mike Travis <travis@....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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists